cve.bz

CVE-2015-8085 huawei: Inadequate Encryption Strength

4.9 mediumEPSS 0.5%

Medium (4.9) in huawei. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
Huawei AR routers with software before V200R007C00SPC100; Quidway S9300 routers with software before V200R009C00; S12700 routers with software before V200R008C00SPC500; S9300, Quidway S5300, and S5300 routers with software before V200R007C00; and S5700 routers with software before V200R007C00SPC500 make it easier for remote authenticated administrators to obtain and decrypt passwords by leveraging selection of a reversible encryption algorithm.

Severity

CVSS 3.0

4.9 medium
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 43rd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-326 Inadequate Encryption Strength
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2015-8085 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2015-8085?via=ask-ai-copy and https://cve.bz/cve/CVE-2015-8085?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2015-8085 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
huawei:s9300_firmwarev200r005c00spc300
huawei:s9300_firmwarev200r006c00spc500
huawei:s12700_firmwarev200r005c00
huawei:s12700_firmwarev200r006c00
huawei:quidway_s9300_firmwarev200r001c00spc300
huawei:quidway_s9300_firmwarev200r002c00spc100
huawei:quidway_s9300_firmwarev200r003c00spc500
huawei:ar_firmwarev200r001
huawei:ar_firmwarev200r002
huawei:ar_firmwarev200r003
huawei:ar_firmwarev200r005c10
huawei:ar_firmwarev200r005c20
huawei:ar_firmwarev200r005c30
huawei:quidway_s5300_firmwarev200r001c00spc300
huawei:s5700_firmwarev200r001c00
huawei:s5700_firmwarev200r002c00
huawei:s5700_firmwarev200r003c00
huawei:s5700_firmwarev200r005c00
huawei:s5700_firmwarev200r006c00
huawei:s5300_firmwarev200r002c00
huawei:s5300_firmwarev200r005c00spc500
huawei:s5300_firmwarev200r006c00spc500

Attack patterns (CAPEC)

  • CAPEC-20 Encryption Brute Forcing Likelihood: Low · Severity: Low
  • CAPEC-112 Brute Force Severity: High
  • CAPEC-192 Protocol Analysis Likelihood: Low · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON