# CVE-2013-6031: Missing authorization in n/a

> Remote attackers can access sensitive information and modify settings on Huawei E355 adapters without authentication due to missing authorization checks on API endpoints.

- **Severity:** Medium 4.3 (`AV:A/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4jv8-r4fh-3jr3

## What is CVE-2013-6031?

CVE-2013-6031 is a medium-severity missing authorization vulnerability in n/a, published on 11 Mar 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2013-6031?

It affects 2 products.


Products: Huawei E355, Huawei E355 Firmware.

## How do I fix CVE-2013-6031?

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

## Is CVE-2013-6031 being exploited?

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

Public exploit code:

- Huawei Datacard Information Disclosure Vulnerability (metasploit)

## Other vulnerabilities in n/a

- [CVE-2014-2968](https://insights.sbomify.com/CVE-2014-2968/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6031 and fix it if it is affected.

What it is: CVE-2013-6031 is a medium-severity missing authorization vulnerability in n/a, published on 11 Mar 2014. 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-2013-6031 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-2013-6031/ (Markdown: https://insights.sbomify.com/CVE-2013-6031/index.md)
```

## Sources

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

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