dbcve.org
Compactlogix 5370 L1 FirmwareOperating system · Rockwellautomation

CVE-2019-10952

CRITICAL · 9.8 CVSS v3.1 Published 2019-05-01
Fix available
A fix is available. Upgrade to after 30.014 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
An attacker could send a crafted HTTP/HTTPS request to render the web server unavailable and/or lead to remote code execution caused by a stack-based buffer overflow vulnerability. A cold restart is required for recovering CompactLogix 5370 L1, L2, and L3 Controllers, Compact GuardLogix 5370 controllers, and Armor Compact GuardLogix 5370 Controllers Versions 20 - 30 and earlier.

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

A stack-based buffer overflow vulnerability in the web server of CompactLogix 5370 L1/L2/L3 and Compact GuardLogix 5370 controllers (versions 20-30 and earlier) allows remote attackers to send crafted HTTP/HTTPS requests, causing denial of service or enabling remote code execution. Cold restart is required for recovery.

MitigationApply vendor firmware updates to affected controllers; until patched, isolate affected devices on separate network segments and restrict web server access to minimize attack surface.

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
Compactlogix 5370 L1 FirmwareOperating system
Affected:>= 20.011, <= 30.014
Compactlogix 5370 L2 FirmwareOperating system
Affected:>= 20.011, <= 30.014
Compactlogix 5370 L3 FirmwareOperating system
Affected:>= 20.011, <= 30.014
Armor Compact Guardlogix 5370 FirmwareOperating system
Affected:>= 20.011, <= 30.014

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 controller model
    Locate the controller model number on the physical device or in the Studio 5000/RSLogix 5000 project properties. Look for CompactLogix 5370 L1, L2, L3, or Armor Compact GuardLogix 5370.
    Affected if Controller is not one of these four models.
  2. Check firmware version
    In Studio 5000, right-click the controller in the Controller Organizer and select Properties. View the Firmware Revision field under the General tab. Alternatively, access via RSLinx Classic using Who Active to view the controller firmware version.
    Affected if Firmware version is 20.011 through 30.014 inclusive.
  3. Verify web server is enabled
    In Studio 5000, go to Controller Properties > Web Server. Confirm the Enable Web Server checkbox is checked. Alternatively, check via the embedded web server page at http://<controller_ip>/ by attempting to access it.
    Affected if Web server is enabled and accessible.
  4. Confirm network accessibility
    Check if the controller IP address is reachable from networks other than a dedicated engineering/OT network. Review firewall rules and network segmentation for the subnet where the controller resides.
    Affected if Controller web server (ports 80/443) is accessible from untrusted networks.

User is affected if they have a CompactLogix 5370 L1/L2/L3 or Armor Compact GuardLogix 5370 controller with firmware version 20.011 to 30.014 and the web server is enabled and accessible.

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 30.014
Interim mitigation

Apply vendor firmware updates to affected controllers; until patched, isolate affected devices on separate network segments and restrict web server access to minimize attack surface.

Recommended fix High confidence

Firmware version 30.015 or later (or latest available version from Rockwell Automation)

  1. Identify the current firmware version of the CompactLogix 5370 L1/L2/L3 or Armor Compact GuardLogix 5370 controller by accessing the controller's properties in Studio 5000 Logix Designer
  2. Download the firmware update package from the official Rockwell Automation Product Compatibility and Download Center (PCDC) at rockwellautomation.custhelp.com
  3. Ensure the controller is in a safe state and coordinate with operations personnel before performing firmware update
  4. Connect to the controller using RSLinx Classic or FactoryTalk Linx
  5. Use ControlFLASH or FactoryTalk Linx Firmware Upgrade feature to flash the controller with the updated firmware (version 30.015 or later)
  6. After firmware update completes, verify the controller returns to RUN mode and validate proper operation
  7. Perform a power cycle of the controller to ensure the new firmware loads correctly and all components initialize properly
  8. Verify web server functionality is restored and the vulnerability is addressed
Caveat Firmware updates may require controller configuration backup before upgrade; verify compatibility with existing project version in Studio 5000

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

Fix this in Compactlogix 5370 L1 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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