CVE-2013-2805
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 · uneditedRockwell Automation RSLinx Enterprise Software (LogReceiver.exe) CPR9, CPR9-SR1, CPR9-SR2, CPR9-SR3, CPR9-SR4, CPR9-SR5, CPR9-SR5.1, and CPR9-SR6 does not handle input correctly and results in a logic error if it receives a datagram with an incorrect value in the “Record Data Size” field. By sending a datagram to the service over Port 4444/UDP with the “Record Data Size” field modified to an oversized value, an attacker could cause an out-of-bounds read access violation that leads to a service crash. The service can be recovered with a manual reboot. The patches and details pertaining to this vulnerability can be found at the following Rockwell Automation Security Advisory link (login is required): https://rockwellautomation.custhelp.com/app/answers/detail/a_id/537599
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 confidenceRockwell Automation RSLinx Enterprise LogReceiver.exe fails to properly validate the 'Record Data Size' field in incoming UDP datagrams on Port 4444/UDP. When an oversized value is provided, the service performs an out-of-bounds read access, causing an access violation and service crash requiring manual reboot.
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.10.00= 5.10.01= 5.20.00= 5.21.00= 5.30.00= 5.40.00= 5.50.00= 5.51.00= 5.60.00CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 RSLinx Enterprise installationLocate the RSLinx Enterprise installation directory, typically in 'C:\Program Files\Rockwell Software\RSLinx Enterprise' or similar. Verify the presence of LogReceiver.exe in the installation folder.Affected if RSLinx Enterprise is installed with LogReceiver.exe present on the system
-
Check installed RSLinx Enterprise versionOpen the Windows Control Panel, go to Programs and Features (or Add/Remove Programs), find 'RSLinx Enterprise' and note the version column. Alternatively, right-click on the RSLinx Enterprise executable in the installation folder, select Properties, and check the Details tab for version information.Affected if The installed version matches one of the affected versions: 5.10.00, 5.10.01, 5.20.00, 5.21.00, 5.30.00, 5.40.00, 5.50.00, 5.51.00, or 5.60.00
-
Verify LogReceiver.exe service statusOpen Windows Services (services.msc) and look for a service related to RSLinx Enterprise LogReceiver, or check running processes for LogReceiver.exe using Task Manager.Affected if The LogReceiver.exe process or service is running on the system
-
Check UDP port 4444 exposureOpen a command prompt and run 'netstat -an | findstr :4444' to verify if Port 4444/UDP is listening. Also check network firewall rules for inbound UDP traffic on port 4444.Affected if Port 4444/UDP is open and listening, or accessible from network segments where untrusted traffic could originate
The environment is affected if RSLinx Enterprise version 5.10.00 through 5.60.00 is installed, LogReceiver.exe is running, and Port 4444/UDP is exposed to untrusted 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 the Rockwell Automation patch from security advisory 537599. As an interim control, restrict network access to Port 4444/UDP to prevent unauthorized datagrams from reaching the affected service.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2805 — 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-2805 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