dbcve.org
RobotwareApplication · Abb

CVE-2024-1913

HIGH · 7.6 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 6.10.10 / 6.13.07 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable 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 who successfully exploited these vulnerabilities could cause the robot to stop, make the robot controller inaccessible, or execute arbitrary code.  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 confidence

A specially crafted message processing vulnerability in ABB RobotWare allows attackers to cause the robot to stop, make the controller inaccessible, or execute arbitrary code. The vulnerability affects IRC5 (RobotWare 6 < 6.15.06 except 6.10.10, and 6.13.07) and OmniCore (RobotWare 7 < 7.14) controllers through specially crafted messages.

MitigationUpdate RobotWare to version 6.15.06+ for IRC5 or 7.14+ for OmniCore. If immediate patching is not feasible, implement network segmentation and restrict access to the robot controller's management interfaces.

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
RobotwareApplication
Affected:>= 6.0.0, < 6.10.10> 6.10.10, < 6.13.07> 6.13.07, < 6.15.06>= 7.00, < 7.14

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 the controller model
    Locate the controller nameplate or check the system documentation for IRC5 or OmniCore identification
    Affected if Controller is an IRC5 or OmniCore robot controller
  2. Check RobotWare version on IRC5
    Access the FlexPendant or use RobotStudio to view System Info under the Controller tab, or run 'rw6 -v' command via service port if available
    Affected if RobotWare version is 6.0.0 to 6.10.09, 6.10.11 to 6.13.06, or 6.13.08 to 6.15.05
  3. Check RobotWare version on OmniCore
    Access the FlexPendant or use RobotStudio to view System Info under the Controller tab, or run 'rw7 -v' command via service port if available
    Affected if RobotWare version is 7.0.0 to 7.13.x
  4. Confirm version is within affected ranges
    Compare your installed version against the affected ranges: IRC5 versions below 6.15.06 (excluding 6.10.10 and 6.13.07) and OmniCore versions below 7.14
    Affected if Installed version matches any of the vulnerable version ranges listed in the CVE

The environment is affected if it uses an IRC5 controller with RobotWare 6 below 6.15.06 (excluding 6.10.10 and 6.13.07) or an OmniCore controller with RobotWare 7 below 7.14

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 6.10.10 / 6.13.07 / 6.15.06 or later
Fixed in 6.10.106.13.076.15.06
Interim mitigation

Update RobotWare to version 6.15.06+ for IRC5 or 7.14+ for OmniCore. If immediate patching is not feasible, implement network segmentation and restrict access to the robot controller's management interfaces.

Recommended fix High confidence

RobotWare 6.15.06+ for IRC5; RobotWare 7.14+ for OmniCore

  1. Identify the current RobotWare version running on the IRC5 or OmniCore controller
  2. For RobotWare 6.x systems: Upgrade to RobotWare version 6.15.06 or later (e.g., 6.16.x)
  3. For RobotWare 7.x systems: Upgrade to RobotWare version 7.14 or later (e.g., 7.15.x)
  4. After upgrade, verify the controller is operational and test critical robot functions
  5. Ensure the controller is behind network segmentation or firewall to limit exposure to untrusted networks
Caveat Review ABB release notes for your specific controller model for any breaking changes or migration considerations before upgrading

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

Fix this in Robotware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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