dbcve.org
Controllogix ControllersApplication · Rockwellautomation

CVE-2012-6437

CRITICAL · 9.8 CVSS v3.1 Published 2013-01-24
Fix available
A fix is available. Upgrade to after 1400 or later.
See remediation →
100/100
Remediation priority · Urgent
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
The device does not properly authenticate users and the potential exists for a remote user to upload a new firmware image to the Ethernet card, whether it is a corrupt or legitimate firmware image. Successful exploitation of this vulnerability could cause loss of availability, integrity, and confidentiality and a disruption in communications with other connected devices. Rockwell Automation EtherNet/IP products; 1756-ENBT, 1756-EWEB, 1768-ENBT, and 1768-EWEB communication modules; CompactLogix L32E and L35E controllers; 1788-ENBT FLEXLogix adapter; 1794-AENTR FLEX I/O EtherNet/IP adapter; ControlLogix 18 and earlier; CompactLogix 18 and earlier; GuardLogix 18 and earlier; SoftLogix 18 and earlier; CompactLogix controllers 19 and earlier; SoftLogix controllers 19 and earlier; ControlLogix controllers 20 and earlier; GuardLogix controllers 20 and earlier; and MicroLogix 1100 and 1400

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

This vulnerability exists in Rockwell Automation EtherNet/IP products where the firmware upload mechanism lacks proper authentication. An unauthenticated remote attacker can upload arbitrary firmware images (corrupt or legitimate) directly to the Ethernet card, compromising availability, integrity, and confidentiality of the device and connected systems.

MitigationImplement network segmentation and firewall controls to restrict access to device management interfaces. Apply vendor-supplied firmware updates. Where patches are unavailable, monitor for unauthorized firmware upload attempts and consider compensating controls such as disabling remote firmware updates.

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
Controllogix ControllersApplication
Affected:<= 20
Guardlogix ControllersApplication
Affected:<= 20
MicrologixApplication
Affected:<= 1100<= 1400
Softlogix ControllersApplication
Affected:<= 19
1756 EnbtHardware / appliance
Affected:all versions
1756 EwebHardware / appliance
Affected:all versions
1768 EnbtHardware / appliance
Affected:all versions
1768 EwebHardware / appliance
Affected:all versions

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify the device model and firmware version
    Access the device through its web interface, RSLinx, or serial console and retrieve the firmware revision. For EtherNet/IP modules (1756-ENBT, 1756-EWEB, etc.), check the module properties in RSLogix/RSLinx. For controllers (Controllogix, Guardlogix, Micrologix, Softlogix), check the controller properties.
    Affected if The firmware version matches or is below the affected versions: Controllogix <=20, Guardlogix <=20, Micrologix 1100 or 1400 <= version 20 (or early revisions), Softlogix <=19, or any version of 1756-ENBT, 1756-EWEB, 1768-ENBT, 1768-EWEB.
  2. Verify if remote firmware upload is enabled
    Check the device configuration for firmware update settings. In the web interface of EtherNet/IP modules (EWEB variants), look under Device Utilities, Firmware Update, or similar sections. In RSLinx, right-click the device and check Properties or Configuration.
    Affected if Remote firmware update functionality is exposed and accessible without authentication requirements.
  3. Assess network accessibility of device management interfaces
    Scan the network for open ports on the device, particularly port 80/HTTP, 443/HTTPS, and the EtherNet/IP CIP ports (2221, 44818). Use tools like nmap or the device's built-in web server to confirm if management interfaces are reachable from untrusted networks.
    Affected if The device web interface or firmware upload features are accessible from network segments that are not strictly controlled or from the internet.
  4. Review firmware upload logs or audit trails
    Examine the device system logs, web server logs, or any available audit logs for entries indicating firmware upload events. Check RSLinx event logs or device web server access logs for firmware-related operations.
    Affected if Any firmware upload activities are logged and show no evidence of authentication enforcement, or if unauthorized uploads are suspected.

The device is affected if it is any model listed in the affected products with a firmware version within the specified ranges or if remote firmware upload is accessible without authentication on any 1756-ENBT/EWEB or 1768-ENBT/EWEB variant.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1400
Interim mitigation

Implement network segmentation and firewall controls to restrict access to device management interfaces. Apply vendor-supplied firmware updates. Where patches are unavailable, monitor for unauthorized firmware upload attempts and consider compensating controls such as disabling remote firmware updates.

Recommended fix Moderate confidence

Firmware versions higher than 20 for ControlLogix/GuardLogix; higher than 19 for SoftLogix/CompactLogix; contact Rockwell Automation for specific fixed versions for MicroLogix 1100/1400 and all ENBT/EWEB modules

  1. 1. Identify the specific Rockwell Automation controller or communication module model and current firmware version
  2. 2. Navigate to the Rockwell Automation Product Compatibility and Download Center (PCDC) at https://compatibility.rockwellautomation.com/
  3. 3. Search for your specific device model (e.g., 1756-ENBT, 1756-EWEB, ControlLogix, GuardLogix, MicroLogix)
  4. 4. Download the latest available firmware version from Rockwell Automation
  5. 5. Follow Rockwell Automation's firmware update instructions specific to your device, typically using RSLinx Classic or ControlFLASH software
  6. 6. Verify the firmware update was successful and test device communications
Caveat Firmware updates on industrial controllers may require compatibility verification with existing projects, ladder logic, and connected devices; test thoroughly in a non-production environment before deploying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Controllogix Controllers Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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