# CVE-2024-6157: Null dereference in RobotWare 6

> An attacker can cause the robot to stop by sending a specially crafted PROFINET message, affecting industrial automation systems.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2024
- **Updated:** 10 Oct 2024
- **Also known as:** GHSA-vfc8-39c7-gmq3

## What is CVE-2024-6157?

CVE-2024-6157 is a medium-severity vulnerability in ABB RobotWare 6, published on 10 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2024-6157?


## How do I fix CVE-2024-6157?

No fix has been published for CVE-2024-6157 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-6157 being exploited?

There is no known exploitation of CVE-2024-6157 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6157 and fix it if it is affected.

What it is: CVE-2024-6157 is a medium-severity vulnerability in ABB RobotWare 6, published on 10 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6157 in the wild and no public exploit code.

Affected product: ABB RobotWare 6. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-6157/ (Markdown: https://insights.sbomify.com/CVE-2024-6157/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-6157
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-6157
- OSV: https://osv.dev/vulnerability/CVE-2024-6157

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-6157/
Summaries are generated and may contain mistakes; the official description above is the record.