CVE-2013-2804
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 DNP Master Driver in Software Toolbox TOP Server before 5.12.140.0 allows remote attackers to cause a denial of service (master-station infinite loop) via crafted DNP3 packets to TCP port 20000 and allows physically proximate attackers to cause a denial of service (master-station infinite loop) via crafted input over a serial line.
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 in Software Toolbox TOP Server before version 5.12.140.0 contains a vulnerability where crafted DNP3 packets sent to TCP port 20000 (or specially crafted input over a serial line) can cause an infinite loop in the master station, resulting in denial of service. The vulnerability is exploitable remotely over the network and by physically proximate attackers via serial connection.
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<= 5.12= 4.0= 5.1= 5.2= 5.3= 5.4= 5.5= 5.6= 5.7= 5.8= 5.9= 5.10CVSS 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.
-
Confirm TOP Server installationCheck for TOP Server process (topserver.exe) in running processes, or look for Software Toolbox TOP Server in Windows Add/Remove Programs.Affected if TOP Server is installed on the system
-
Identify installed TOP Server versionOpen TOP Server interface, check the About/Help section, or examine the executable file properties of topsever.exe for version information.Affected if Version is 4.0, 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, 5.7, 5.8, 5.9, 5.10, or any version up to and including 5.12
-
Verify DNP Master Driver is configuredCheck TOP Server configuration for an active DNP3 Master Driver session or channel. This is typically visible in the TOP Server setup or runtime interface.Affected if A DNP Master Driver session is active and communicating
-
Check network exposure on TCP port 20000Run netstat -an or use a port scanner to verify if TCP port 20000 is listening. Also verify firewall rules permitting this port.Affected if TCP port 20000 is open and listening on a network interface accessible to attackers
-
Check for serial DNP3 connectionsReview TOP Server configuration for any serial (RS-232/RS-485) connections configured for DNP3 protocol.Affected if Serial DNP3 connections are configured and active
A user is affected if TOP Server with a vulnerable version (4.0, 5.1-5.10, or <=5.12) is running with the DNP Master Driver enabled and TCP port 20000 or serial DNP3 is exposed to untrusted attackers.
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 TOP Server to version 5.12.140.0 or later. Additionally, restrict network access to TCP port 20000 through firewalls or network segmentation to reduce the remote attack surface.
- Consultation3.0 h
- Implementation4.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 $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2804 — 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-2804 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