# CVE-2015-8231: Denial of service in n/a

> Remote attackers with established sessions can cause Huawei IP phones to restart via unspecified packets, resulting in denial of service.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jan 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2837-pj7h-9v2g

## What is CVE-2015-8231?

CVE-2015-8231 is a high-severity denial of service vulnerability in n/a, published on 11 Jan 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Huawei eSpace 7910 and 7950 IP phones with software before V200R002C00SPC800 allow remote attackers with established sessions to cause a denial of service (device restart) via unspecified packets.

Weakness: CWE-399

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

It affects 2 products.


Products: Huawei Espace 7910, Huawei Espace 7950.

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

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

## Is CVE-2015-8231 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-8231 is a high-severity denial of service vulnerability in n/a, published on 11 Jan 2016. 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-8231 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-8231/ (Markdown: https://insights.sbomify.com/CVE-2015-8231/index.md)
```

## Sources

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

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