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

> Remote attackers can cause a denial of service on Zhone GPON devices by sending a long string in the oldpassword parameter.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 23 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wpfg-h6pp-74wp

## What is CVE-2015-2055?

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

### Official description

Zhone GPON 2520 with firmware R4.0.2.566b allows remote attackers to cause a denial of service via a long string in the oldpassword parameter.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Zhone Technologies Gpon 2520 Firmware.

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

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

## Is CVE-2015-2055 being exploited?

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

Public exploit code:

- Zhone GPON 2520 R4.0.2.566b - Crash (PoC) (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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