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

> Remote attackers can cause a denial of service in Huawei unified gateways by sending crafted SSH packets to the CLI module.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Nov 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f389-983q-vhv9

## What is CVE-2015-7845?

CVE-2015-7845 is a medium-severity denial of service vulnerability in n/a, published on 19 Nov 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The exception handling mechanism in the CLI Module in Huawei eSpace U1910, U1911, U1930, U1960, U1980, and U1981 unified gateways with software before V100R001C20SPH605 allows remote attackers to cause a denial of service (CLI outage) via crafted SSH packets.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Huawei Espace Firmware.

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

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

## Is CVE-2015-7845 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-8083](https://insights.sbomify.com/CVE-2015-8083/): Memory corruption in n/a (high 7.8)
- [CVE-2015-8229](https://insights.sbomify.com/CVE-2015-8229/): Denial of service in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-7845 is a medium-severity denial of service vulnerability in n/a, published on 19 Nov 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-7845 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-7845/ (Markdown: https://insights.sbomify.com/CVE-2015-7845/index.md)
```

## Sources

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

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