# CVE-2015-3911: Auth bypass in n/a

> Remote attackers can bypass authentication to modify configurations, send messages, and restart the device.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:N/C:P/I:P/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rq2q-54mj-gpp7

## What is CVE-2015-3911?

CVE-2015-3911 is a critical authentication bypass vulnerability in n/a, published on 21 May 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Huawei E587 Mobile WiFi with firmware before 11.203.30.00.00 allows remote attackers to bypass authentication, change configurations, send messages, and cause a denial of service (device restart) via unspecified vectors.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2015-3911?

It affects 1 product.


Products: Huawei E587 Mobile Wifi Firmware.

## How do I fix CVE-2015-3911?

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

## Is CVE-2015-3911 being exploited?

There is no known exploitation of CVE-2015-3911 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3911 and fix it if it is affected.

What it is: CVE-2015-3911 is a critical authentication bypass vulnerability in n/a, published on 21 May 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-3911 in the wild and no public exploit code.

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-2015-3911/ (Markdown: https://insights.sbomify.com/CVE-2015-3911/index.md)
```

## Sources

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

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