CVE-2024-2424
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 · uneditedAn input validation vulnerability exists in the Rockwell Automation 5015-AENFTXT that causes the secondary adapter to result in a major nonrecoverable fault (MNRF) when malicious input is entered. If exploited, the availability of the device will be impacted, and a manual restart is required. Additionally, a malformed PTP packet is needed to exploit this vulnerability.
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 confidenceA input validation vulnerability exists in the Rockwell Automation 5015-AENFTXT secondary adapter that allows malformed PTP (Precision Time Protocol) packets to trigger a major nonrecoverable fault (MNRF), causing device unavailability and requiring manual restart.
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= 2.011CVSS 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.
-
Confirm device model is 5015-AENFTXTAccess the device management interface or check the physical device label to verify the model number is exactly 5015-AENFTXT secondary adapter.Affected if Device model is not 5015-AENFTXT - not affected by this specific CVE.
-
Check firmware versionLog into the device admin console or use Rockwell's update utility to view the installed firmware version. Look for a firmware version reported as 2.011.Affected if Firmware version equals 2.011 - this is the exact affected version.
-
Verify PTP protocol is enabledAccess the device network configuration settings and check if Precision Time Protocol (PTP) is enabled or configured. PTP is typically found under time synchronization or network settings.Affected if PTP is enabled - the device is processing PTP traffic and could be exploited.
-
Inspect device logs for MNRF eventsReview the device event logs or system logs for entries indicating Major Nonrecoverable Fault (MNRF) events, especially if they coincide with PTP packet processing.Affected if Recent MNRF faults are logged - indicates potential exploitation attempts.
-
Monitor network for PTP trafficUse a network sniffer or IDS to capture and inspect PTP (IEEE 1588) packets on the network segment connected to the device. Look for malformed or anomalous PTP packets.Affected if Malformed PTP packets are observed targeting this device - active exploitation indicator.
You are affected if you have a 5015-AENFTXT device running firmware version 2.011 with PTP protocol enabled and processing network traffic.
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 PTP traffic to trusted sources, and monitor for anomalous PTP packets. Consider firmware updates from Rockwell if available.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2424 — 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-2424 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