CVE-2013-2791
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 · uneditedMatrikonOPC SCADA DNP3 OPC Server 1.2.0 allows remote attackers to cause a denial of service (master-station daemon crash) via a malformed DNP3 TCP packet from the IP address of an outstation.
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 confidenceMatrikonOPC SCADA DNP3 OPC Server 1.2.0 contains a vulnerability where malformed DNP3 TCP packets sent from an outstation's IP address can crash the master-station daemon, causing a denial of service. DNP3 is a SCADA/ICS communication protocol used between outstations and master stations.
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= 1.2.0CVSS 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 MatrikonOPC DNP3 Server versionCheck the product version through the Windows Add/Remove Programs dialog, the software's About section, or by reviewing installation logs and registry keys under HKLM\SOFTWARE\Matrikon or the installed program directory for version information.Affected if The installed version is exactly 1.2.0
-
Confirm DNP3 protocol is configuredReview the MatrikonOPC DNP3 Server configuration to verify that DNP3 master station functionality is enabled and configured to communicate with outstations. Check the server configuration files or management interface for active DNP3 bindings.Affected if DNP3 master functionality is enabled and the server is configured to accept connections from outstations
-
Verify network exposure of DNP3 serviceCheck Windows Firewall settings, network configuration, and any host-based or perimeter firewall rules to determine if the DNP3 service TCP port (typically port 20000 or configured DNP3 port) is open to network traffic.Affected if The DNP3 service port is exposed to network and reachable from outstation IP addresses
-
Check for recent service crashesReview Windows Event Viewer Application and System logs, as well as any MatrikonOPC-specific logs, for recent crash events or service restart entries related to the DNP3 server daemon.Affected if The master-station daemon has crashed or restarted unexpectedly and logs indicate malformed DNP3 packets as the cause
A user is affected if they have MatrikonOPC SCADA DNP3 OPC Server version 1.2.0 specifically, with DNP3 master functionality enabled and the service exposed to network traffic from outstations.
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 available vendor patches to update MatrikonOPC DNP3 OPC Server to a patched version. Until patched, implement network segmentation to isolate SCADA systems and deploy DNP3-aware firewall rules to filter malformed packets.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2791 — 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-2791 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