CVE-2013-2811
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 (1) Catapult DNP3 I/O driver before 7.2.0.60 and the (2) GE Intelligent Platforms Proficy DNP3 I/O driver before 7.20k, as used in DNPDrv.exe (aka the DNP master station server) in GE Intelligent Platforms Proficy HMI/SCADA - CIMPLICITY and iFIX, 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 confidenceThis vulnerability exists in DNP3 I/O drivers (Catapult and GE Intelligent Platforms Proficy) used in GE HMI/SCADA systems (CIMPLICITY and iFIX). Remote attackers can send specially crafted DNP3 TCP packets that cause an infinite loop in the DNP master station server (DNPDrv.exe), resulting in denial of service.
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<= 7.20.56<= 7.20= 7.20= 4.01= 7.5= 8.0= 8.1= 8.2= 5.0= 5.1CVSS 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 installed Catapult DNP3 I/O Driver versionCheck the version of Catapultsoftware Catapult Dnp3 I/O Driver in Programs and Features or by locating the driver DLL/version file in the installation directoryAffected if The installed version is 7.20.56 or lower
-
Identify installed GE Proficy DNP3 I/O Driver versionCheck the version of GE Intelligent Platforms Proficy Dnp3 I/O Driver in Programs and Features or by locating the driver DLL/version file in the installation directoryAffected if The installed version is 7.20 or lower (including exactly 7.20)
-
Identify installed CIMPLICITY versionCheck the version of GE Intelligent Platforms Proficy HMI/SCADA CIMPLICITY in Programs and Features or the CIMPLICITY About dialogAffected if The installed version is exactly 4.01, 7.5, 8.0, 8.1, or 8.2
-
Identify installed iFIX versionCheck the version of GE Intelligent Platforms Proficy HMI/SCADA iFIX in Programs and Features or the iFIX About dialogAffected if The installed version is exactly 5.0 or 5.1
-
Verify DNP3 driver is runningCheck if the DNPDrv.exe process is running on the system using Task Manager or command line tools like tasklist /FI "IMAGENAME eq DNPDrv.exe"Affected if DNPDrv.exe is actively running, indicating DNP3 functionality is enabled and the vulnerability can be triggered
A system is affected if it has any of the vulnerable DNP3 I/O drivers or HMI/SCADA products installed in the specified versions AND has DNP3 functionality enabled (DNPDrv.exe running).
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 dataUpdate the Catapult DNP3 I/O driver to version 7.2.0.60 or later, and the GE Proficy DNP3 I/O driver to version 7.20k or later. If immediate patching is not feasible, implement network segmentation and firewall rules to restrict unauthorized access to DNP3 services.
- 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-2811 — 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-2811 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