dbcve.org
Rslinx EnterpriseApplication · Rockwellautomation

CVE-2013-2806

HIGH · 7.5 CVSS v3.0 Published 2019-03-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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
Rockwell 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 calculates an incorrect value for the “End of Current Record” field. By sending a datagram to the service over Port 4444/UDP with the “Record Data Size” field modified to a specifically oversized value, the service will calculate an undersized value for the “Total Record Size.” Then the service will calculate an incorrect value for the “End of Current Record” field causing access violations that lead to a service crash. The service can be recovered with a manual reboot. The patches and details pertaining to these vulnerabilities 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 confidence

RSLinx Enterprise LogReceiver.exe contains a logic error when calculating the 'End of Current Record' field. By sending a crafted UDP datagram to port 4444 with an oversized 'Record Data Size' value, the service computes incorrect 'Total Record Size' and 'End of Current Record' values, triggering access violations and causing the service to crash. Recovery requires manual system reboot.

MitigationApply the Rockwell Automation patch for affected versions (CPR9 through CPR9-SR6) from security advisory 537599. As an interim control, block or restrict UDP port 4444 at network boundaries to prevent unauthenticated attackers from reaching the vulnerable service.

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
Rslinx EnterpriseApplication
Affected:= 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.00

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

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

  1. Verify RSLinx Enterprise is installed
    Locate RSLinx Enterprise installation on the system - check Program Files directory for Rockwell Software folder, or use system inventory tools to identify if this software is present
    Affected if RSLinx Enterprise software is installed on the system
  2. Identify installed RSLinx Enterprise version
    Check the installed version of RSLinx Enterprise through Windows Programs and Features, or inspect version information in the application executable or installation directory
    Affected if Installed version matches any of: 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
  3. Locate LogReceiver.exe component
    Find LogReceiver.exe in the RSLinx Enterprise installation directory - this is the vulnerable component that processes the malformed UDP datagrams
    Affected if LogReceiver.exe exists in the RSLinx Enterprise installation folder
  4. Check if UDP port 4444 is listening
    Use netstat -an or similar network scanning tool to determine if UDP port 4444 is open and listening - this is the port where the vulnerable service receives incoming datagrams
    Affected if UDP port 4444 is exposed and listening on the system

The system is affected if RSLinx Enterprise is installed with a version matching the affected list AND LogReceiver.exe is present AND UDP port 4444 is accessible (even if locally), as the service can be crashed by a crafted UDP datagram to that port.

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 the Rockwell Automation patch for affected versions (CPR9 through CPR9-SR6) from security advisory 537599. As an interim control, block or restrict UDP port 4444 at network boundaries to prevent unauthenticated attackers from reaching the vulnerable service.

Fix this in Rslinx Enterprise Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-2806 — 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-2013-2806 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