CVE-2013-6143
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 · uneditedThe Schneider Electric Telvent SAGE 3030 RTU with firmware C3413-500-001D3_P4 and C3413-500-001F0_PB allows remote attackers to cause a denial of service (temporary outage and CPU consumption) via malformed DNP3 traffic.
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 Schneider Electric Telvent SAGE 3030 RTU with firmware versions C3413-500-001D3_P4 and C3413-500-001F0_PB contains a denial-of-service vulnerability where malformed DNP3 traffic can cause temporary outages and excessive CPU consumption on the device.
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= c3413-500-001d3_p4= c3413-500-001f0_pbCVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 device modelQuery the device or check its nameplate/documentation to confirm it is a Schneider Electric Telvent SAGE 3030 RTUAffected if The device is not a Telvent SAGE 3030 RTU
-
Check the installed firmware versionAccess the device console or management interface and retrieve the firmware version string. Common commands include 'show version' or accessing the system information pageAffected if The firmware version is exactly C3413-500-001D3_P4 or exactly C3413-500-001F0_PB
-
Verify DNP3 protocol is enabledCheck the device configuration for DNP3 protocol settings. Inspect the protocol configuration menu or configuration files for DNP3 enable statusAffected if DNP3 protocol is enabled and active on the device
-
Assess network exposure of DNP3 serviceCheck if DNP3 ports (typically UDP/TCP port 20000) are accessible from untrusted network segments. Review firewall rules and network ACLs protecting the RTUAffected if DNP3 traffic from untrusted sources can reach the device
The device is affected if it is a Telvent SAGE 3030 RTU running firmware version C3413-500-001D3_P4 or C3413-500-001F0_PB, has DNP3 enabled, and the DNP3 service is reachable from untrusted network sources.
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 available firmware patches from Schneider Electric and implement network segmentation to limit exposure of the RTU to untrusted DNP3 traffic sources.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6143 — 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-2013-6143 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