# CVE-2024-5801: IP Forwarding enabled in B&R Automation Runtime

> Enabled IP forwarding in B&R Automation Runtime allows attackers to bypass network security controls by routing packets through the host.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L`)
- **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 Aug 2024
- **Updated:** 12 Aug 2024
- **Also known as:** GHSA-pgr9-55pc-cmx2

## What is CVE-2024-5801?

CVE-2024-5801 is a medium-severity vulnerability in B&R Industrial Automation Automation Runtime, published on 10 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Enabled IP Forwarding feature in B&R Automation Runtime versions before 6.0.2 may allow remote attack-ers to compromise network security by routing IP-based packets through the host, potentially by-passing firewall, router, or NAC filtering.

Weakness: CWE-653 (Improper Isolation or Compartmentalization), CWE-1188 (Initialization of a Resource with an Insecure Default)

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


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

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

## Is CVE-2024-5801 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-5801 is a medium-severity vulnerability in B&R Industrial Automation Automation Runtime, published on 10 Aug 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-5801 in the wild and no public exploit code.

Affected product: B&R Industrial Automation Automation Runtime. 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-5801/ (Markdown: https://insights.sbomify.com/CVE-2024-5801/index.md)
```

## Sources

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

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