# CVE-2016-1337: Information disclosure in n/a

> Remote attackers can obtain sensitive configuration and credential information from Cisco EPC3928 devices by making requests during the early boot process.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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:** 3 Jul 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jmc5-w94v-7p94

## What is CVE-2016-1337?

CVE-2016-1337 is a high-severity vulnerability in n/a, published on 3 Jul 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco EPC3928 devices allow remote attackers to obtain sensitive configuration and credential information by making requests during the early part of the boot process, related to a "Boot Information Disclosure" issue, aka Bug ID CSCux17178.

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

## Which versions are affected by CVE-2016-1337?

It affects 1 product.


Products: Cisco Epc3928 Firmware.

## How do I fix CVE-2016-1337?

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

## Is CVE-2016-1337 being exploited?

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

Public exploit code:

- Cisco EPC 3928 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2016-1328](https://insights.sbomify.com/CVE-2016-1328/): Denial of service in n/a (high 7.5)
- [CVE-2016-1336](https://insights.sbomify.com/CVE-2016-1336/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1337 and fix it if it is affected.

What it is: CVE-2016-1337 is a high-severity vulnerability in n/a, published on 3 Jul 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-2016-1337 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-2016-1337/ (Markdown: https://insights.sbomify.com/CVE-2016-1337/index.md)
```

## Sources

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

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