CVE-2014-9697
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHuawei USG9560/9520/9580 before V300R001C01SPC300 allows remote attackers to cause a memory leak or denial of service (memory exhaustion, reboot and MPU switchover) via a crafted website.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA memory leak vulnerability in Huawei USG9560/9520/9580 security gateways allows remote attackers to send crafted website requests that exhaust device memory, causing denial of service through memory exhaustion, device reboot, and MPU (Main Processing Unit) switchover. The vulnerability exists in versions prior to V300R001C01SPC300.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= v300r001c00= v300r001c01spc100= v300r001c00= v300r001c01spc100= v300r001c00= v300r001c01spc100CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device modelLog into the device CLI or check the device label to confirm the model is USG9560, USG9520, or USG9580.Affected if Device is not one of these three models, then not affected.
-
Check firmware versionRun the command 'display version' in the device CLI to retrieve the current firmware version.Affected if Version displayed is v300r001c00 or v300r001c01spc100.
-
Verify management interface exposureCheck if the web management interface (HTTP/HTTPS) is accessible from untrusted networks using 'display ip interface' or reviewing the firewall security policy configuration.Affected if The web interface is exposed to untrusted networks and the firmware version is vulnerable.
-
Monitor memory usageRun 'display memory' or 'display cpu-usage' periodically to observe memory consumption patterns and check for abnormal memory growth.Affected if Memory usage shows continuous increase or exhaustion, especially when web requests are processed.
If the device is a USG9560/9520/9580 running firmware v300r001c00 or v300r001c01spc100 with the management interface exposed to untrusted networks, the device is affected by this memory leak vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Huawei USG firmware to version V300R001C01SPC300 or later. If immediate patching is not feasible, implement network-level access controls to restrict exposure of the management interface to untrusted networks.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-9697 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-9697 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data