Security readout for executives and security teams
Plain-English summary
A flaw in Rockwell Automation RSLinx Enterprise LogReceiver.exe can make the service crash after malformed UDP traffic. In an industrial environment, the main business risk is loss of a supporting communications or logging service until someone manually reboots the affected system.
Executive priority
Treat this as a targeted OT availability risk. Prioritize remediation where affected systems support production operations or are reachable from broad internal networks.
Technical view
Affected CPR9 through CPR9-SR6 releases miscalculate Total Record Size when Record Data Size is oversized, causing an out-of-bounds read access violation and service crash. The issue is classified as CWE-190 and is associated with UDP port 4444 handling in LogReceiver.exe.
Likely exposure
Exposure is most likely where affected RSLinx Enterprise versions are still deployed and LogReceiver.exe is reachable over UDP port 4444, especially across flat OT networks or from less trusted segments.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The vulnerability is described as a remote service crash condition requiring crafted network input, with recovery by manual reboot.
Researcher notes
Evidence is limited to CVE text and the public ICS-CERT reference; Rockwell patch details require login. Do not assume code execution, privilege escalation, or active exploitation from the provided sources.
Mitigation direction
- Obtain and apply Rockwell Automation patches or guidance from the referenced advisory.
- Restrict UDP port 4444 to trusted OT hosts only.
- Segment affected engineering and control networks from general IT networks.
- Monitor affected systems for unexpected LogReceiver.exe crashes or required reboots.
- Confirm vendor support status for CPR9 through CPR9-SR6 deployments.
Validation and detection
- Inventory RSLinx Enterprise installations and record exact CPR9 service release levels.
- Confirm whether LogReceiver.exe is present and enabled on those systems.
- Review firewall rules for UDP port 4444 reachability.
- Check operational logs for repeated service crashes or unexplained reboots.
- Validate patch status against Rockwell Automation advisory 537599.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2013-2807 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://ics-cert.us-cert.gov/advisories/ICSA-13-095-02CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.