CVE-2012-6570
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 · uneditedThe HTTP module in the (1) Branch Intelligent Management System (BIMS) and (2) web management components on Huawei AR routers and S2000, S3000, S3500, S3900, S5100, S5600, S7800, and S8500 switches does not check whether HTTP data is longer than the value of the Content-Length field, which allows remote HTTP servers to conduct heap-based buffer overflow attacks and execute arbitrary code via a crafted response.
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 confidenceThe HTTP client module in affected Huawei network devices fails to validate that incoming HTTP response data length matches the Content-Length header value. A malicious remote HTTP server can send a response with body data exceeding the declared Content-Length, causing a heap-based buffer overflow that enables arbitrary code execution on the targeted device.
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<= r0130<= r1712<= r0118<= r2207<= r0311= r6305= r6305= r6305CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 and run 'display device' or 'display version' to confirm the exact model number (e.g., AR 18 1x, AR 18 2x, AR 19, AR 28, S2000, S2300, S2700)Affected if Device model is not one of: AR 18 1x, AR 18 2x, AR 18 3x, AR 19, AR 29, AR 49, AR 28, AR 46, S2000, S2300, S2700
-
Check firmware versionRun 'display version' or 'display firmware version' to retrieve the firmware revision number (e.g., r0130, r1712, r2207, r6305)Affected if Firmware version falls within or below these thresholds: AR 18 1x <= r0130, AR 18 2x <= r1712, AR 18 3x <= r0118, AR 19/29/49 <= r2207, AR 28/46 <= r0311, S2000/S2300/S2700 = r6305
-
Verify HTTP client feature statusRun 'display http client' or check HTTP client configuration via 'display current-configuration | include http' to see if the device has HTTP client functionality configuredAffected if HTTP client feature is enabled or configured on the device (device initiates outbound HTTP connections to remote servers)
-
Check HTTP management interfaceRun 'display http server' or 'display ip http' to see if HTTP management interface is activeAffected if HTTP management interface is enabled, as this may expose the HTTP client module to untrusted servers
Device is affected only if it is a listed model, runs a firmware version at or below the specified threshold, AND has HTTP client functionality enabled or HTTP management interface active.
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 dataApply Huawei firmware updates for affected AR router and switch models. If updates are unavailable, restrict device HTTP client connections to trusted servers only and disable unused HTTP management interfaces.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6570 — 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-2012-6570 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