# CVE-2015-7847: Denial of service in E3272s Versions earlier than E3272s-153TCPU-V200R002B491D09SP00C00

> An attacker can cause a denial of service on Huawei MBB devices by sending malicious packets to the CGI interface.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5jr7-43r3-xcf7

## What is CVE-2015-7847?

CVE-2015-7847 is a medium-severity denial of service vulnerability in E3272s Versions earlier than E3272s-153TCPU-V200R002B491D09SP00C00, published on 2 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Huawei MBB (Mobile Broadband) product E3272s with software versions earlier than E3272s-153TCPU-V200R002B491D09SP00C00 has a Denial of Service (DoS) vulnerability. An attacker could send a malicious packet to the Common Gateway Interface (CGI) of a target device and make it fail while setting the port attribute, which causes a DoS attack.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Huawei E3272s Firmware.

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

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

## Is CVE-2015-7847 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-7847 is a medium-severity denial of service vulnerability in E3272s Versions earlier than E3272s-153TCPU-V200R002B491D09SP00C00, published on 2 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-7847 in the wild and no public exploit code.

Affected product: E3272s Versions earlier than E3272s-153TCPU-V200R002B491D09SP00C00. 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-7847/ (Markdown: https://insights.sbomify.com/CVE-2015-7847/index.md)
```

## Sources

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

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