dbcve.org
Zenon Dnp3 Ng DriverApplication · Copadata

CVE-2014-2345

HIGH · 7.1 CVSS v2.0 Published 2014-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
COPA-DATA zenon DNP3 NG driver (DNP3 master) 7.10 and 7.11 through 7.11 SP0 build 10238 and zenon DNP3 Process Gateway (DNP3 outstation) 7.11 SP0 build 10238 and earlier allow remote attackers to cause a denial of service (infinite loop and process crash) by sending a crafted DNP3 packet over TCP.

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 confidence

The COPA-DATA zenon DNP3 protocol drivers (both master and outstation) contain a vulnerability where parsing a specially crafted DNP3 packet over TCP triggers an infinite loop, causing the process to crash and resulting in denial of service. The issue affects versions 7.10 through 7.11 SP0 build 10238. The vulnerability is network-exploitable and requires no authentication.

MitigationApply available vendor patches for zenon versions 7.10 and 7.11 to address the DNP3 packet parsing flaw; if patches are unavailable, implement network segmentation and firewall rules to restrict untrusted sources from reaching the DNP3 services.

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
Zenon Dnp3 Ng DriverApplication
Affected:= 7.10= 7.11
Zenon Dnp3 Process GatewayApplication
Affected:= 7.11

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify zenon DNP3 driver installation
    Check the installed programs or zenon installation directory for 'zenon DNP3 NG Driver' or 'zenon DNP3 Process Gateway' components. Use Windows 'Programs and Features' or check the zenon installation path (typically C:\Program Files\COPA-DATA\zenon) for DNP3-related executables or DLLs.
    Affected if Either the 'zenon Dnp3 Ng Driver' or 'zenon Dnp3 Process Gateway' component is installed on the system.
  2. Determine zenon version
    Right-click the zenon editor or runtime executable, select 'Properties', then view the 'Version' tab. Alternatively, check the zenon installation directory for version information in the program files or check the Windows registry under HKLM\SOFTWARE\COPA-DATA\zenon for the installed version.
    Affected if The installed zenon version is 7.10 or 7.11 (any build up to and including 10238).
  3. Verify DNP3 protocol is enabled
    Open the zenon project editor and navigate to the driver or process gateway configuration. Check if DNP3 NG Driver or DNP3 Process Gateway is added and enabled in the project tree under 'Drivers' or 'Process Gateways'. Check the project configuration files (.zprj) for DNP3 driver entries.
    Affected if The DNP3 driver or process gateway is configured and enabled in the zenon project.
  4. Check network exposure of DNP3 service
    Review firewall rules and network configuration to determine if DNP3 TCP ports (typically port 20000 for DNP3) are exposed to untrusted networks. Use 'netstat -an' or Windows Firewall advanced security settings to list listening ports associated with zenon DNP3 services.
    Affected if The DNP3 service is listening on TCP ports accessible from untrusted or external networks.

A user is affected if zenon version 7.10 or 7.11 is installed with DNP3 NG Driver or DNP3 Process Gateway enabled and the DNP3 service is network-accessible, since specially crafted DNP3 packets can trigger the infinite loop crash.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available vendor patches for zenon versions 7.10 and 7.11 to address the DNP3 packet parsing flaw; if patches are unavailable, implement network segmentation and firewall rules to restrict untrusted sources from reaching the DNP3 services.

Fix this in Zenon Dnp3 Ng Driver Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-2345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-2345 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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