cve.bz

CVE-2015-7846 huawei

4.6 mediumEPSS 0.3%

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

On this page
Huawei S7700, S9700, S9300 before V200R07C00SPC500, and AR200, AR1200, AR2200, AR3200 before V200R005C20SPC200 allows attackers with physical access to the CF card to obtain sensitive information.

Severity

CVSS 3.0

4.6 medium
CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 18th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
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-7846 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2015-7846?via=ask-ai-copy and https://cve.bz/cve/CVE-2015-7846?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-7846 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_firmwarev200r001c00spc300
huawei:s9300_firmwarev200r002c00spc100
huawei:s9300_firmwarev200r003c00spc500
huawei:s9300_firmwarev200r005c00spc300
huawei:s9300_firmwarev200r006c00spc300
huawei:s9300_firmwarev200r006c00spc500
huawei:s9700_firmwarev200r001c00spc300
huawei:s9700_firmwarev200r002c00spc100
huawei:s9700_firmwarev200r003c00spc500
huawei:s9700_firmwarev200r005c00spc300
huawei:s9700_firmwarev200r006c00spc300
huawei:s9700_firmwarev200r006c00spc500
huawei:s7700_firmwarev200r001c00spc300
huawei:s7700_firmwarev200r002c00spc100
huawei:s7700_firmwarev200r003c00spc500
huawei:s7700_firmwarev200r005c00spc300
huawei:s7700_firmwarev200r006c00spc300
huawei:s7700_firmwarev200r006c00spc500
huawei:ar200_firmwarev200r003c00spc100
huawei:ar200_firmwarev200r003c00spc200
huawei:ar200_firmwarev200r003c01spc100
huawei:ar200_firmwarev200r003c01spc200
huawei:ar200_firmwarev200r003c01spc300
huawei:ar200_firmwarev200r003c01spc500
huawei:ar200_firmwarev200r003c01spc600
huawei:ar200_firmwarev200r003c01spc800
huawei:ar200_firmwarev200r003c01spc900
huawei:ar1200_firmwarev200r003c00spc100
huawei:ar1200_firmwarev200r003c00spc200
huawei:ar1200_firmwarev200r003c01spc100
huawei:ar1200_firmwarev200r003c01spc200
huawei:ar1200_firmwarev200r003c01spc300
huawei:ar1200_firmwarev200r003c01spc500
huawei:ar1200_firmwarev200r003c01spc600
huawei:ar1200_firmwarev200r003c01spc800
huawei:ar1200_firmwarev200r003c01spc900
huawei:ar2200_firmwarev200r003c00spc100
huawei:ar2200_firmwarev200r003c00spc200
huawei:ar2200_firmwarev200r003c01spc100
huawei:ar2200_firmwarev200r003c01spc200
huawei:ar2200_firmwarev200r003c01spc300
huawei:ar2200_firmwarev200r003c01spc500
huawei:ar2200_firmwarev200r003c01spc600
huawei:ar2200_firmwarev200r003c01spc800
huawei:ar2200_firmwarev200r003c01spc900
huawei:ar3200_firmwarev200r003c00spc100
huawei:ar3200_firmwarev200r003c00spc200
huawei:ar3200_firmwarev200r003c01spc100
huawei:ar3200_firmwarev200r003c01spc200
huawei:ar3200_firmwarev200r003c01spc300
huawei:ar3200_firmwarev200r003c01spc500
huawei:ar3200_firmwarev200r003c01spc600
huawei:ar3200_firmwarev200r003c01spc800
huawei:ar3200_firmwarev200r003c01spc900

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON