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

> Remote attackers can read sensitive information from improperly initialized Ethernet packet padding in Eaton ProView relays.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 23 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qcr8-g26g-46hc

## What is CVE-2015-6471?

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

### Official description

Eaton Cooper Power Systems ProView 4.x and 5.x before 5.1 on Form 6 controls and Idea and IdeaPLUS relays does not properly initialize padding fields in Ethernet packets, which allows remote attackers to obtain sensitive information by reading packet data.

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

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

It affects 1 product.


Products: Eaton Proview.

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

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

## Is CVE-2015-6471 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-9196](https://insights.sbomify.com/CVE-2014-9196/): Eaton’s Cooper Power Series Form 6 Control and Idea/IdeaPlus Relays with Ethernet (high 7.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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