CVE-2013-2792
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 · uneditedSchweitzer Engineering Laboratories (SEL) SEL-2241, SEL-3505, and SEL-3530 RTAC master devices allow remote attackers to cause a denial of service (infinite loop) via a crafted DNP3 TCP 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 SEL-2241, SEL-3505, and SEL-3530 RTAC master devices contain a vulnerability in their DNP3 protocol implementation. Attackers can send crafted DNP3 TCP packets to trigger an infinite loop, causing denial of service. The vulnerability is exploitable remotely without authentication.
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= r113-v0-z001001-d20110721= r123-v0-z002001-d20130117= r119-v0-z001001-d20120720= r123-v0-z002001-d20130117= r100_-v0-z001001-d20090915= r123-v0-z002001= r107-v0-z001001-d20100818= r123-v0-z002001-d20130117CVSS 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
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:M/Au:N/C:N/I:N/A:C
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 SEL RTAC device modelAccess the device configuration or use SNMP/sysinfo to determine if the device is an SEL-2241, SEL-3505, SEL-3530, or SEL-3530 4 modelAffected if The device model is any of: SEL-2241, SEL-3505, SEL-3530, or SEL-3530 4
-
Check the installed firmware versionUse the device command line interface (e.g., 'version' or 'show firmware') or access the web interface System Information page to retrieve the firmware version stringAffected if The firmware version matches or falls between the affected versions: r113, r119, r100, r107, or r123 (specifically r113-v0-z001001-d20110721, r123-v0-z002001-d20130117, r119-v0-z001001-d20120720, r100_-v0-z001001-d20090915, r107-v0-z001001-d20100818, or r123-v0-z002001)
-
Verify if DNP3 protocol is enabledCheck the device configuration for DNP3 settings - access the protocol configuration menu or use 'show config dnp3' command to see if DNP3 master or outstation is configuredAffected if DNP3 is enabled and configured on the device (the vulnerability exists in the DNP3 implementation regardless of role)
-
Determine DNP3 network exposureReview firewall rules and network configuration to check if TCP port 20000 (standard DNP3) or configured DNP3 ports are accessible from untrusted networksAffected if DNP3 service is reachable from external or untrusted network segments without filtering
A user is affected if they have an SEL-2241, SEL-3505, SEL-3530, or SEL-3530 4 device running any of the vulnerable firmware versions listed AND DNP3 protocol is enabled on the device.
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 vendor-supplied firmware updates when available. Implement network segmentation and firewall rules to restrict DNP3 traffic to authorized sources only. Monitor for anomalous DNP3 traffic patterns.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2792 — 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-2792 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