Loading vulnerability…
Multiple Huawei networking and security products store passwords using the DES algorithm. Because DES is a weak/obsolete cryptographic algorithm for password protection, an attacker who obtains the stored/encrypted password data can perform offline brute-force cracking to recover cleartext credentials, enabling subsequent unauthorized access to the affected device(s).
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository provides a Python script (Decrypt.py) that exploits the weak password encryption (DES with a static key) vulnerability in multiple Huawei routers and switches (CVE-2012-4960). The script takes a 24-character encrypted password string, decodes it, and decrypts it using the DES algorithm with a hardcoded key (\x01\x02\x03\x04\x05\x06\x07\x08) in ECB mode. The decrypted output is the plaintext password used on the device. The README.md lists a wide range of affected Huawei products and provides usage instructions. The exploit is a proof-of-concept for offline password decryption and does not target network services directly. No network endpoints or IP addresses are present in the code. The repository structure is simple, containing the main script, a README, a license, and a .gitignore file.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.