CVE-2024-1914
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 attacker who successfully exploited these vulnerabilities could cause the robot to stop, make the robot controller inaccessible. The vulnerability could potentially be exploited to perform unauthorized actions by an attacker. This vulnerability arises under specific condition when specially crafted message is processed by the system. Below are reported vulnerabilities in the Robot Ware versions. * IRC5- RobotWare 6 < 6.15.06 except 6.10.10, and 6.13.07 * OmniCore- RobotWare 7 < 7.14
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 and potential unauthorized action vulnerability in ABB RobotWare robot controllers (both IRC5 and OmniCore). The vulnerability is triggered when the system processes specially crafted malicious messages, which can cause the robot to stop and render the controller inaccessible. The attack appears to require network access to the controller's communication channels.
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>= 6.0.0, < 6.10.10> 6.10.10, < 6.13.07> 6.13.07, < 6.15.06>= 7.00, < 7.14CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 installed RobotWare versionAccess the robot controller's system information interface or use the controller's diagnostic tools to retrieve the RobotWare software version numberAffected if The version falls within any of the affected ranges: >= 6.0.0 and < 6.10.10; > 6.10.10 and < 6.13.07; > 6.13.07 and < 6.15.06; or >= 7.0 and < 7.14
-
Determine the controller typeIdentify whether the affected system is an IRC5 or OmniCore controller, as the fixed versions differ between these product linesAffected if The controller is either IRC5 or OmniCore and the version is in the affected range
-
Assess network exposure of controller communication channelsReview network configuration and firewall rules to determine if the robot controller's communication ports are accessible from untrusted networksAffected if The controller's network interfaces are exposed to untrusted or external networks without proper segmentation
-
Verify accessible communication servicesIdentify which controller communication services (such as RAPID execution interfaces, PC interfaces, or fieldbus connections) are enabled and listening on the networkAffected if Network-accessible communication services are enabled and the controller version is vulnerable
-
Review access controls on controller interfacesExamine authentication settings and access control lists on the robot controller to determine if untrusted clients can send messages to the controllerAffected if The controller accepts messages from untrusted network sources and the version is in the affected range
The environment is affected if the installed RobotWare version is within any of the affected version ranges AND the controller's network communication channels are accessible from untrusted networks.
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.
dbcve · scoped6.10.106.13.076.15.06
Upgrade ABB RobotWare to version 6.15.06 or later for IRC5 controllers, or version 7.14 or later for OmniCore controllers. If upgrading is not immediately feasible, network segmentation and access controls should be implemented to limit exposure to untrusted networks.
RobotWare 6.15.06+ (for 6.x versions) or RobotWare 7.14+ (for 7.x versions)
- 1. Identify the current RobotWare version installed on the controller via the FlexPendant or RobotStudio
- 2. For IRC5 controllers running RobotWare 6.x: Plan upgrade to RobotWare 6.15.06 or later
- 3. For OmniCore controllers running RobotWare 7.x: Plan upgrade to RobotWare 7.14 or later
- 4. Backup all robot programs, system parameters, and configurations before performing the upgrade
- 5. Obtain the appropriate RobotWare upgrade media from ABB
- 6. Follow ABB's standard RobotWare upgrade procedure via RobotStudio or FlexPendant
- 7. After upgrade, verify controller accessibility and robot functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1914 — 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-1914 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