CVE-2013-6031 json
The Huawei E355 adapter with firmware 21.157.37.01.910 does not require authentication for API pages, which allows remote attackers to chan…
published 12y ago modified 4mo ago also EUVD-2013-5861
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.1%
- EPSS 6.1% chance of exploitation in 30 days, percentile 93%
- public exploits
- 1
- Metasploit
Summary
The Huawei E355 adapter with firmware 21.157.37.01.910 does not require authentication for API pages, which allows remote attackers to change passwords and settings, or obtain sensitive information, via a direct request to (1) api/wlan/security-settings, (2) api/device/information, (3) api/wlan/basic-settings, (4) api/wlan/mac-filter, (5) api/monitoring/status, or (6) api/dhcp/settings.
Is CVE-2013-6031 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (Metasploit auxiliary/gather/huawei_wifi_info)
- Published
Exploit prediction
6.08% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit auxiliary/gather/huawei_wifi_info Huawei Datacard Information Disclosure Vulnerability metasploit auxiliary, normal rank, 2013-11-11
- github.com https://github.com/aczire/huawei-csrf-info_disclosure/blob/master/huawei_wifi_info.rb referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:A/AC:M/Au:N/C:P/I:P/A:N |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
github.com
/aczire/huawei-csrf-info_disclosure/blob/master/huawei_wifi_info.rb
exploit
-
kb.cert.org
/vuls/id/341526
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2013-6031
- NVD CVE-2013-6031
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.