dbcve.org
AcuHardware / appliance · Huawei

CVE-2012-4960

MEDIUM · 6.5 CVSS v2.0 Published 2013-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The Huawei NE5000E, MA5200G, NE40E, NE80E, ATN, NE40, NE80, NE20E-X6, NE20, ME60, CX600, CX200, CX300, ACU, WLAN AC 6605, S9300, S7700, S2300, S3300, S5300, S3300HI, S5300HI, S5306, S6300, S2700, S3700, S5700, S6700, AR G3, H3C AR(OEM IN), AR 19, AR 29, AR 49, Eudemon100E, Eudemon200, Eudemon300, Eudemon500, Eudemon1000, Eudemon1000E-U/USG5300, Eudemon1000E-X/USG5500, Eudemon8080E/USG9300, Eudemon8160E/USG9300, Eudemon8000E-X/USG9500, E200E-C/USG2200, E200E-X3/USG2200, E200E-X5/USG2200, E200E-X7/USG2200, E200E-C/USG5100, E200E-X3/USG5100, E200E-X5/USG5100, E200E-X7/USG5100, E200E-B/USG2100, E200E-X1/USG2100, E200E-X2/USG2100, SVN5300, SVN2000, SVN5000, SVN3000, NIP100, NIP200, NIP1000, NIP2100, NIP2200, and NIP5100 use the DES algorithm for stored passwords, which makes it easier for context-dependent attackers to obtain cleartext passwords 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 · high confidence

Multiple Huawei network device models (routers, switches, firewalls, WLAN controllers) store passwords using the weak DES encryption algorithm. This symmetric cipher with its small 56-bit key space is vulnerable to brute-force attacks, allowing attackers who obtain the password hashes to recover cleartext credentials.

MitigationReplace DES-based password storage with modern cryptographic algorithms (AES, bcrypt, or PBKDF2) and update affected device firmware to versions that support strong password hashing. Force password changes for all accounts after applying the update.

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
AcuHardware / appliance
Affected:= v100r003c01spc100= v200r001c00= v200r001c00spc100
Ar 19\/29\/49Hardware / appliance
Affected:<= r2207
Ar G3Hardware / appliance
Affected:= v200r001c00= v200r001c01= v200r002c00spc200
AtnHardware / appliance
Affected:= v200r001c00= v200r001c01
Cx200Hardware / appliance
Affected:= v100r005
Cx300Hardware / appliance
Affected:= v100r005
Cx600Hardware / appliance
Affected:= v200r002= v600r001= v600r002= v600r003
E200 Usg2200Hardware / appliance
Affected:<= v200r003c00

CVSS 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
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Huawei device model
    Log into the device or check device documentation to determine the exact model (e.g., Acu, Ar 19/29/49, Ar G3, Atn, Cx200, Cx300, Cx600, E200 Usg2200)
    Affected if The device model is one of the listed affected product lines (Acu, Ar, Atn, Cx, E200 Usg2200 series)
  2. Determine the firmware/software version
    Use the device CLI command 'display version' or check the web interface/system info page to find the installed firmware version
    Affected if The firmware version is known and can be compared against affected version ranges
  3. Compare version against affected ranges for Acu
    If device is Acu, check if version equals v100r003c01spc100, v200r001c00, or v200r001c00spc100
    Affected if The installed version matches exactly one of these three versions
  4. Compare version against affected ranges for Ar 19/29/49
    If device is Ar 19, 29, or 49 series, check if version is r2207 or lower
    Affected if The version is r2207 or any earlier version (e.g., r2206, r2205)
  5. Compare version against affected ranges for Ar G3
    If device is Ar G3, check if version equals v200r001c00, v200r001c01, or v200r002c00spc200
    Affected if The installed version matches exactly one of these three versions
  6. Compare version against affected ranges for other models
    For Atn check v200r001c00 or v200r001c01; for Cx200/Cx300 check v100r005; for Cx600 check v200r002, v600r001, v600r002, or v600r003; for E200 Usg2200 check v200r003c00 or lower
    Affected if The installed version matches exactly one of the listed affected versions for that product line

The device is affected if it is a Huawei Acu, Ar 19/29/49, Ar G3, Atn, Cx200, Cx300, Cx600, or E200 Usg2200 model running a firmware version that matches one of the specific affected versions listed in the CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace DES-based password storage with modern cryptographic algorithms (AES, bcrypt, or PBKDF2) and update affected device firmware to versions that support strong password hashing. Force password changes for all accounts after applying the update.

Fix this in Acu Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-4960 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-4960 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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