dbcve.org
NULL Pointer DereferenceWeakness · CWE-476

CVE-2024-6157

MEDIUM · 5.1 CVSS v3.1 Published 2024-10-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
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 who successfully exploited these vulnerabilities could cause the robot to stop. A vulnerability exists in the PROFINET stack included in the RobotWare versions listed below.  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

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 denial of service vulnerability in the PROFINET stack in ABB RobotWare allows remote attackers to cause robots to stop by sending specially crafted network messages. The vulnerability affects IRC5 controllers running RobotWare versions 6 < 6.15.06 (except 6.10.10) and 6.13.07.

MitigationApply vendor patches by upgrading to RobotWare 6.15.06 or later. If patching is not immediately feasible, implement network segmentation and PROFINET traffic filtering to reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:L/AC:H/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 the controller type
    Confirm the system is an ABB IRC5 controller. This vulnerability only affects IRC5 controllers, not other ABB robotics controllers.
    Affected if System is not an IRC5 controller (not affected)
  2. Check RobotWare version
    Access the robot controller pendant or use the FlexPendant to view System Info. Navigate to About > System Information to find the RobotWare version number.
    Affected if RobotWare version is 6.x below 6.15.06 (excluding 6.10.10) OR version is exactly 6.13.07
  3. Verify PROFINET configuration
    Check if PROFINET is enabled on the controller. On the FlexPendant, go to Controller > Configuration > I/O > Industrial Network to confirm PROFINET is configured and active.
    Affected if PROFINET is not configured or not in use (the vulnerability requires PROFINET to be enabled)
  4. Confirm network exposure
    Review network topology to determine if the PROFINET interface is accessible to untrusted network segments. Check if the controller IP is reachable from outside the local robot cell network.
    Affected if PROFINET interface is exposed to untrusted or external networks

You are affected if you have an IRC5 controller with RobotWare version 6.x below 6.15.06 (excluding 6.10.10) or exactly 6.13.07, with PROFINET enabled and accessible to the attack vector.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches by upgrading to RobotWare 6.15.06 or later. If patching is not immediately feasible, implement network segmentation and PROFINET traffic filtering to reduce attack surface.

Recommended fix Moderate confidence

RobotWare 6.15.06 or later

  1. 1. Identify the current RobotWare version running on the IRC5 controller using the FlexPendant or System Information
  2. 2. Confirm the installed version is RobotWare 6 < 6.15.06 (excluding 6.10.10 and 6.13.07)
  3. 3. Obtain the RobotWare 6.15.06 or later update package from ABB (available via ABB Customer Web or local ABB service representative)
  4. 4. Back up the current robot system configuration and programs
  5. 5. Install RobotWare 6.15.06 or later following ABB's standard RobotWare upgrade procedures
  6. 6. After upgrade, verify the PROFINET stack is functioning correctly and test robot operations
Caveat Review ABB RobotWare 6.15 release notes for any changes to PROFINET configuration or controller functionality that may require system reconfiguration

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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