# CVE-2024-8603: Weak cryptography in Automation Runtime

> Unauthenticated attackers can masquerade as services on B&R Automation Runtime devices due to weak cryptographic algorithms in SSL/TLS.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jan 2025
- **Updated:** 15 Jan 2025
- **Also known as:** GHSA-pc9x-x955-fmg3

## What is CVE-2024-8603?

CVE-2024-8603 is a high-severity vulnerability in B&R Industrial Automation Automation Runtime, published on 15 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A “Use of a Broken or Risky Cryptographic Algorithm” vulnerability in the SSL/TLS component used in B&R Automation Runtime versions before 6.1 and B&R mapp View versions before 6.1 may be abused by unauthenticated network-based attackers to masquerade as services on impacted devices.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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


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

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

## Is CVE-2024-8603 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8603 is a high-severity vulnerability in B&R Industrial Automation Automation Runtime, published on 15 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8603 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-8603/ (Markdown: https://insights.sbomify.com/CVE-2024-8603/index.md)
```

## Sources

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

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