# CVE-2012-4960: Weak cryptography in n/a

> Attackers can brute-force DES-encrypted stored passwords on various Huawei network devices to obtain cleartext credentials.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-45v5-mvm5-gw3v

## What is CVE-2012-4960?

CVE-2012-4960 is a medium-severity vulnerability in n/a, published on 20 Jun 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-310

## Which versions are affected by CVE-2012-4960?

It affects 66 products.


Products: Huawei Acu, Huawei Ar 19\/29\/49, Huawei Ar G3, Huawei Atn, Huawei Cx200, Huawei Cx300, Huawei Cx600, Huawei E200 Usg2200, Huawei E200 Usg5100, Huawei E200e-B, Huawei E200e-C, Huawei E200e-Usg2100, Huawei E200e-X1, Huawei E200e-X2, Huawei E200x3, Huawei E200x5, Huawei E200x7, Huawei Eudemon1000, Huawei Eudemon1000e-U, Huawei Eudemon1000e-X and 46 more.

## How do I fix CVE-2012-4960?

No fix has been published for CVE-2012-4960 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-4960 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-4960 exists.

Public exploit code:

- Huawei (Multiple Products) - Password Encryption (exploitdb)
- Code to decrypt Huawei passwords CVE-2012-4960 (github_poc): https://github.com/ghcohu/Decrypt-passwords-for-Huawei-routers-and-switches-CVE-2012-4960

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4960 and fix it if it is affected.

What it is: CVE-2012-4960 is a medium-severity vulnerability in n/a, published on 20 Jun 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-4960 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-4960/ (Markdown: https://insights.sbomify.com/CVE-2012-4960/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-4960
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-4960
- OSV: https://osv.dev/vulnerability/CVE-2012-4960

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-4960/
Summaries are generated and may contain mistakes; the official description above is the record.