CVE-2012-4695
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 · uneditedLogReceiver.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 (service outage) via a zero-byte UDP packet that is not properly handled 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 confidenceLogReceiver.exe in Rockwell Automation RSLinx Enterprise fails to properly validate zero-byte UDP packets in Logger.dll, causing the service to crash and remain unavailable. The vulnerability is remotely exploitable via network access to the affected service's UDP port.
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
- 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.
-
Identify installed RSLinx Enterprise versionLocate RSLinx Enterprise installation and check its version information. This may be found in Windows Programs and Features, the installation directory, or the application's About/Help dialog. Compare the version to the affected version: cpr9.Affected if The installed version of RSLinx Enterprise is exactly cpr9.
-
Confirm RSLinx Enterprise UDP service is runningCheck if the LogReceiver.exe process or related RSLinx Enterprise services are actively running on the system. Use Task Manager or command 'tasklist /FI "IMAGENAME eq LogReceiver.exe"' to list running instances.Affected if LogReceiver.exe or associated RSLinx Enterprise services are running and listening for UDP connections.
-
Identify open UDP ports used by RSLinx EnterpriseUse 'netstat -an | findstr UDP' to list all listening UDP ports on the system. Identify which UDP port RSLinx Enterprise uses for its logging/receiver service. Cross-reference with any documentation or network scans of the environment.Affected if RSLinx Enterprise has a UDP port open and listening for network traffic.
-
Assess network exposure of the UDP serviceReview firewall rules, network segmentation, and ACLs to determine whether untrusted network sources can send UDP packets to the RSLinx Enterprise server. Use 'netsh advfirewall firewall show rule name=all' or check border firewall configurations.Affected if The UDP port used by RSLinx Enterprise is accessible from untrusted network segments or external addresses.
You are affected if RSLinx Enterprise version cpr9 is installed, its UDP service is running and network-accessible, and untrusted network sources can send packets to that 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 network segmentation and firewall rules to restrict UDP traffic to RSLinx Enterprise components from untrusted sources. Contact Rockwell Automation for available patches or firmware updates addressing this vulnerability.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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 $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4695 — 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-4695 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