CVE-2014-5429
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 · uneditedDNP Master Driver 3.02 and earlier in Elipse SCADA 2.29 build 141 and earlier, E3 1.0 through 4.6, and Elipse Power 1.0 through 4.6 allows remote attackers to cause a denial of service (CPU consumption) via malformed packets.
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 DNP Master Driver 3.02 and earlier in Elipse SCADA, E3, and Elipse Power products contains a vulnerability where malformed network packets can trigger excessive CPU consumption, leading to denial of service. The vulnerability is remotely exploitable and affects the DNP3 protocol master driver component used in SCADA/ICS environments.
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<= 2.29<= 4.6<= 4.6CVSS 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 Elipse product installedCheck the installed software on the system for Elipse SCADA, Elipse E3, or Elipse Power. Look in Add/Remove Programs (Windows) or check the installation directory for recognizable product binaries or executables.Affected if Any Elipse SCADA, E3, or Power product is installed on the system
-
Determine the installed versionOpen the application's About or Help section, or right-click the main executable and view Properties > Details to find the version or build number. Compare this against the affected ranges: Elipse SCADA <= 2.29, Elipse Power <= 4.6, Elipse E3 <= 4.6.Affected if The installed version falls within or below these affected version numbers
-
Verify if DNP Master Driver is loadedCheck the application configuration or runtime loaded modules for the DNP Master Driver component. Look in the application's driver or I/O configuration settings for DNP3 or DNP Master entries.Affected if The DNP Master Driver is present and configured in the application
-
Check network exposure of DNP serviceReview network firewall rules and listening ports on the affected system. The DNP3 protocol typically uses TCP/UDP ports 20000 or similar. Determine if these ports are accessible from untrusted networks.Affected if The system is reachable from untrusted networks on ports used by the DNP Master Driver
A user is affected if they have Elipse SCADA <= 2.29, Elipse Power <= 4.6, or Elipse E3 <= 4.6 with the DNP Master Driver enabled and exposed to network 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 vendor patches by updating to Elipse SCADA versions beyond build 141, E3 beyond 4.6, and Elipse Power beyond 4.6. Additionally, network segmentation and firewall controls should limit exposure of affected systems to untrusted networks.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5429 — 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-2014-5429 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