# CVE-2015-6428: Information disclosure in n/a

> Remote attackers can obtain sensitive information from Cisco DPQ3925 devices via crafted HTTP requests.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2c45-fqp9-5vw6

## What is CVE-2015-6428?

CVE-2015-6428 is a medium-severity vulnerability in n/a, published on 18 Dec 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco DPQ3925 devices with EDVA r1 Base allow remote attackers to obtain sensitive information via a crafted HTTP request, aka Bug ID CSCuv03958.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Cisco Dpq3925 8x4 Docsis 3.0 Wireless Residential Gateway With Embedded Digital Voice Adapter.

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

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

## Is CVE-2015-6428 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-1326](https://insights.sbomify.com/CVE-2016-1326/): Denial of service in n/a (high 7.5)
- [CVE-2015-6378](https://insights.sbomify.com/CVE-2015-6378/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-6428 is a medium-severity vulnerability in n/a, published on 18 Dec 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-6428 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-6428/ (Markdown: https://insights.sbomify.com/CVE-2015-6428/index.md)
```

## Sources

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

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