CVE-2014-0761
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 DNP3 driver in CG Automation ePAQ-9410 Substation Gateway allows remote attackers to cause a denial of service (infinite loop or process crash) via a crafted 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 · moderate confidenceThe DNP3 driver in CG Automation ePAQ-9410 Substation Gateway contains a vulnerability where processing a crafted TCP packet triggers an infinite loop or process crash, causing denial of service. The vulnerability is exploitable remotely without authentication, indicating insufficient input validation in the DNP3 protocol handling code.
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 dataall versionsCVSS 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 ePAQ-9410 device presenceInventory network devices and check for CG Automation or Qeiinc ePAQ-9410 Substation Gateway devices via SNMP, network scanning, or asset management recordsAffected if The ePAQ-9410 Substation Gateway device exists in the environment
-
Locate DNP3 service port exposureScan network for open TCP ports associated with DNP3 protocol (commonly port 20000 or configurable ports). Use network scanning tools or review firewall rules to identify exposed DNP3 servicesAffected if The DNP3 service port is listening and accessible on the network
-
Verify remote accessibility without authenticationCheck firewall rules, ACLs, and network segmentation to determine if the DNP3 port accepts connections from untrusted or external network segmentsAffected if The DNP3 service can be reached remotely without authentication from untrusted networks
-
Confirm DNP3 protocol handler is enabledReview device configuration or documentation to verify the DNP3 driver is actively enabled and processing protocol traffic on the deviceAffected if The DNP3 driver is enabled and processing traffic on the device
If the ePAQ-9410 Substation Gateway is present with DNP3 driver enabled and the service port is network-accessible from untrusted sources, the environment is affected by this CVE.
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 firmware patches for the ePAQ-9410 device; if patches are unavailable, implement network segmentation and firewall rules to restrict untrusted access to the DNP3 service port.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0761 — 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-0761 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