CVE-2012-6569
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 · uneditedStack-based buffer overflow in the 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 allows remote attackers to execute arbitrary code via a long URI.
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 confidenceStack-based buffer overflow in the HTTP service module on specific Huawei network devices (AR routers and S-series switches). Attackers can send a specially crafted HTTP request with an abnormally long URI to overflow a stack buffer, potentially executing arbitrary code with the privileges of the HTTP service.
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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 your Huawei device modelLog into the device CLI and run 'display version' or 'display device' to confirm the model number (AR 18xx, AR 19/29/49, AR 28/46, S2000, S2300, or S2700)Affected if The device is one of the listed model families and the firmware version falls within the affected ranges
-
Check your firmware versionRun 'display version' in the device CLI to obtain the firmware/compatible version numberAffected if The version is at or below r0130 for AR 18-1x, r1712 for AR 18-2x, r0118 for AR 18-3x, r2207 for AR 19/29/49, r0311 for AR 28/46, or r6305 for S2000/S2300/S2700
-
Verify if HTTP service is enabledRun 'display ip http' or 'display http server status' to check if the HTTP management service is activeAffected if HTTP service is enabled and running on the device
-
Check HTTP management access controlRun 'display acl all' or review the HTTP service binding interface configuration to see if HTTP is bound to any interfaceAffected if HTTP service is bound to a management interface that is accessible from untrusted networks
You are affected if your device is a listed Huawei AR or S-series model with a firmware version at or below the specified threshold AND the HTTP service is enabled and accessible.
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 security patches or firmware updates that address the HTTP module vulnerability. If patches are unavailable, restrict HTTP management access to trusted networks or disable the HTTP management interface in favor of SSH.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6569 — 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-6569 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