CVE-2012-6571
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, and S7800 switches uses predictable Session ID values, which makes it easier for remote attackers to hijack sessions via a brute-force attack.
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 · moderate confidenceThe HTTP module in Huawei BIMS and web management components on AR routers and S2000-S7800 switch series uses predictable session ID values, allowing remote attackers to hijack sessions through brute-force attacks.
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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Verify HTTP management interface is enabledLog into the device CLI and run 'display http server' or check if HTTP port 80 is listening (using 'display ip interface' or network port scan)Affected if HTTP management is enabled and accessible - the vulnerability only applies when HTTP web management is active
-
Check the firmware versionRun 'display version' or 'display device version' in the CLI to identify the installed firmware revision (e.g., r0130, r1712, r2207, r0311, r6305)Affected if The firmware version matches or is below the affected versions: 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
-
Confirm web-based management is in useCheck if the device has web management enabled by running 'display web' or 'display http server' and verify the service is activeAffected if Web management UI is enabled - this is required for the predictable session ID flaw to be exploitable
-
Assess management interface accessibilityReview ACLs or firewall rules applied to the management interface (Vlan1, Loopback0, or dedicated management port) to determine if HTTP port 80 is reachable from untrusted networksAffected if HTTP management interface is exposed to untrusted networks (internet or user-facing VLANs) - remote attackers need network access to brute-force session IDs
A user is affected if they are running one of the listed firmware versions AND have HTTP web management enabled AND that interface is accessible to potential attackers.
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 dataReplace or upgrade to patched firmware; until then, disable HTTP management, use HTTPS if available, and restrict management interface access to trusted IPs.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6571 — 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-6571 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