CVE-2024-6077
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 · uneditedA denial-of-service vulnerability exists in the Rockwell Automation affected products when specially crafted packets are sent to the CIP Security Object. If exploited the device will become unavailable and require a factory reset to recover.
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 · moderate confidenceThis is a denial-of-service vulnerability in Rockwell Automation industrial control products. Attackers send specially crafted packets to the CIP (Common Industrial Protocol) Security Object, causing the device to become unresponsive and unavailable. The severity is elevated by the fact that affected devices require a factory reset to recover, causing significant operational disruption.
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= 32.011= 32.013= 32.011= 32.011= 33.011= 32.011= 2.001CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device model and firmware versionConnect to the controller using RSLogix 5000/Studio 5000 or access the device web interface. Navigate to the controller properties or system information to view the firmware revision number.Affected if The firmware version matches exactly 32.011 for Compactlogix 5380, 32.013 for Compact Guardlogix 5380 SIL 2, 32.011 for Compact Guardlogix 5380 SIL 3, 32.011 for Compactlogix 5480, 33.011 for Controllogix 5580, 32.011 for Guardlogix 5580, or 2.001 for 1756 EN4.
-
Confirm CIP Security Object is configuredIn RSLogix/Studio 5000, expand the controller hierarchy and locate the CIP Security Object (typically under Security or System tree). Check if the CIP Security object exists and is enabled in the device configuration.Affected if The CIP Security Object is present and enabled on the controller.
-
Verify network exposure of CIP portsReview network firewall rules or access control lists. Identify if UDP and TCP port 44818 (CIP) is open to untrusted or unauthorized network segments. Use network scanning tools or review firewall configurations.Affected if The device is reachable on CIP ports (44818/UDP, 44818/TCP) from network segments that are not explicitly trusted or segmented.
-
Check for anomalous CIP trafficMonitor network traffic logs or IDS/IPS alerts for unusual patterns targeting the CIP Security Object. Review any existing logs for packet anomalies or repeated connection attempts to CIP services.Affected if Unusual or malformed CIP packets are observed targeting the security object, or the device becomes unresponsive during the monitoring period.
You are affected if your device model matches one of the listed products AND the firmware version exactly matches the vulnerable version AND CIP Security Object is enabled, especially if the device is network-accessible from untrusted segments.
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 dataImplement network segmentation and firewall rules to restrict unauthorized access to industrial control devices. Monitor for anomalous CIP traffic and apply any vendor-supplied patches when available. Consider network intrusion detection to identify malicious packet patterns targeting the CIP Security Object.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6077 — 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-2024-6077 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