CVE-2012-4715
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 · uneditedBuffer overflow in LogReceiver.exe in Rockwell Automation RSLinx Enterprise CPR9, CPR9-SR1, CPR9-SR2, CPR9-SR3, CPR9-SR4, CPR9-SR5, CPR9-SR5.1, and CPR9-SR6 allows remote attackers to cause a denial of service (daemon crash) or possibly execute arbitrary code via a UDP packet with a certain integer length value that is (1) too large or (2) too small, leading to improper handling by Logger.dll.
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 confidenceBuffer overflow vulnerability in LogReceiver.exe within Rockwell Automation RSLinx Enterprise versions CPR9 through CPR9-SR6. The vulnerability is triggered by sending specially crafted UDP packets with integer length values that are either too large or too small, causing improper handling in Logger.dll. This can lead to denial of service or potentially arbitrary code execution.
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= cpr9CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/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.
-
Locate RSLinx Enterprise installationSearch for the RSLinx Enterprise installation directory, typically found under C:\Program Files\Rockwell Software\RSLinx Enterprise or C:\Program Files (x86)\Rockwell Software\RSLinx Enterprise. Verify the LogReceiver.exe binary exists in the installation folder.Affected if The LogReceiver.exe binary is present and the software version is CPR9 through CPR9-SR6
-
Identify installed versionRight-click on LogReceiver.exe in the installation directory, select Properties, then navigate to the Details tab to view the File Version. Alternatively, open RSLinx Enterprise and check Help > About RSLinx Enterprise for the exact CPR version.Affected if The displayed version falls within the CPR9 through CPR9-SR6 range
-
Verify LogReceiver.exe service statusOpen Windows Services (services.msc) and look for a service related to LogReceiver or RSLinx Enterprise logging. Alternatively, open Task Manager and check for LogReceiver.exe running as a process.Affected if The LogReceiver.exe process or service is currently running
-
Confirm UDP listener is activeOpen Command Prompt and run 'netstat -an | findstr UDP' to list all UDP endpoints. Look for ports associated with RSLinx Enterprise logging, typically UDP port 4446 or similar logging ports. Cross-reference with RSLinx documentation for the expected UDP port.Affected if A UDP listener is bound to a port used by LogReceiver.exe and the service is accessible on the network
A user is affected if RSLinx Enterprise is installed with version CPR9 through CPR9-SR6 AND the LogReceiver.exe service is running with an exposed UDP port.
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 vendor patches for RSLinx Enterprise CPR9-SR6 or later. If patching is not immediately feasible, implement network segmentation and firewall rules to restrict UDP traffic to the LogReceiver.exe service.
- Consultation4.0 h
- Implementation8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4715 — 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-2012-4715 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