dbcve.org
Compactlogix 5370 L1 FirmwareOperating system · Rockwellautomation

CVE-2019-10954

HIGH · 7.5 CVSS v3.1 Published 2019-05-01
Fix available
A fix is available. Upgrade to after 30.014 or later.
See remediation →
84/100
Remediation priority · High
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 crafted SMTP packets to cause a denial-of-service condition where the controller enters a major non-recoverable faulted state (MNRF) in 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

This vulnerability exists in Rockwell Automation CompactLogix 5370 and GuardLogix 5370 controllers where specially crafted SMTP packets can trigger a denial-of-service condition, causing the controller to enter a major non-recoverable faulted state (MNRF). The vulnerability affects versions 20-30 and earlier of these controllers.

MitigationUpdate controller firmware to a version beyond 30 to patch the SMTP vulnerability; if immediate patching is not possible, implement network segmentation and filter/block inbound SMTP traffic to affected controllers.

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
Compact Guardlogix 5370 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 hardware and verify it is one of the following: CompactLogix 5370 L1, CompactLogix 5370 L2, CompactLogix 5370 L3, GuardLogix 5370, or Armor Compact GuardLogix 5370. Check the model number label on the controller chassis or review the project hardware configuration in Studio 5000 Logix Designer.
    Affected if The controller is any model other than the five listed models.
  2. Check firmware version
    In Studio 5000 Logix Designer, go to the Controller Properties or use RSLinx Classic to query the controller firmware revision. Alternatively, access the controller web page if available and view the firmware revision information.
    Affected if The firmware version is between 20.011 and 30.014 inclusive.
  3. Verify SMTP is enabled
    In Studio 5000 Logix Designer, open Controller Properties and navigate to the Communication or SMTP settings panel. Check if SMTP email functionality is configured or enabled. You can also inspect the controller's message configuration for any MSG instructions using SMTP.
    Affected if SMTP email functionality is configured, enabled, or any MSG instructions using SMTP are present in the project.
  4. Assess network exposure
    Review network architecture to determine if the controller has any network path that could allow inbound SMTP packets (TCP port 25) from untrusted sources. Check firewall rules, switch configurations, and VLAN assignments.
    Affected if The controller is reachable on TCP port 25 from any network segment that contains untrusted or external systems.

You are affected if you have a CompactLogix 5370 or GuardLogix 5370 controller with firmware version 20.011 through 30.014 that has SMTP enabled and is exposed to network SMTP traffic.

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.

From vendor data
Upgrade available Upgrade to a release after 30.014
Interim mitigation

Update controller firmware to a version beyond 30 to patch the SMTP vulnerability; if immediate patching is not possible, implement network segmentation and filter/block inbound SMTP traffic to affected controllers.

Fix this in Compactlogix 5370 L1 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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