CVE-2015-6485
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSchneider 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Telvent Sage RTUs (multiple models including Sage 2300, 1410, 1430, 1450, 2400, 3030M, and LANDAC II-2) contain an information disclosure vulnerability where sensitive data from device memory is leaked through the padding field of Ethernet packets. An unauthenticated remote attacker can capture these packets to extract potentially sensitive information from the device memory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= c3414-500-s02j1<= c3413-500-001d3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the exact RTU modelPhysically inspect the device or access its management interface to confirm the model number (Sage 2300, 1410, 1430, 1450, 2400, 3030M, or LANDAC II-2).Affected if The device is any of these Telvent Sage models.
-
Check the installed firmware versionAccess the device firmware or system information via its management interface or console, and note the exact firmware build string (such as c3414-500-s02j1 or c3413-500-001d3).Affected if The firmware version is c3414-500-s02j1 or earlier, OR c3413-500-001d3 or earlier.
-
Verify network accessibility of the RTUConfirm whether the RTU Ethernet interface is reachable from network segments accessible to unauthenticated users or untrusted networks.Affected if The device is accessible on the network without authentication barriers.
-
Capture Ethernet traffic from the deviceUse a network sniffer on the segment connected to the RTU to capture outgoing Ethernet packets and inspect the padding field of each packet for unexpected data patterns or potential memory contents.Affected if Padding fields contain data other than zeros or expected values, indicating memory leakage.
The environment is affected if the RTU is a Telvent Sage model (2300, 1410, 1430, 1450, 2400, 3030M, or LANDAC II-2) running firmware c3414-500-s02j1 or earlier (or c3413-500-001d3 or earlier for Sage 2300), and the device is network-accessible to capture its Ethernet traffic.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor-supplied firmware updates: upgrade Sage 2300 to C3413-500-S01 or later, and upgrade all other affected models to C3414-500-S02J2 or later. Since these are ICS/RTU devices, plan the firmware update during a maintenance window and test thoroughly in a non-production environment first.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6485 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-6485 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data