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

> Remote attackers can read sensitive information from device memory by exploiting a padding field in Ethernet packets on Schneider Electric RTUs.

- **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:** 12 Mar 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7qxm-j3q6-829g

## What is CVE-2015-6485?

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

### Official description

Schneider Electric Telvent Sage 2300 RTUs with firmware before C3413-500-S01, and LANDAC II-2, Sage 1410, Sage 1430, Sage 1450, Sage 2400, and Sage 3030M RTUs with firmware before C3414-500-S02J2, allow remote attackers to obtain sensitive information from device memory by reading a padding field of an Ethernet packet.

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

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

It affects 1 product.


Products: Schneider-Electric Telvent Rtu Firmware.

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

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

## Is CVE-2015-6485 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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