# CVE-2024-54089: Weak cryptography in APOGEE PXC Series (BACnet)

> Attackers can decrypt passwords using a hard-coded key in Siemens APOGEE and TALON controllers, potentially leading to unauthorized access.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/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:** 11 Feb 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-v68j-53vw-j6rw

## What is CVE-2024-54089?

CVE-2024-54089 is a high-severity vulnerability in Siemens APOGEE PXC Series (BACnet), published on 11 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been identified in APOGEE PXC Series (BACnet) (All versions), APOGEE PXC Series (P2 Ethernet) (All versions), TALON TC Series (BACnet) (All versions). Affected devices contain a weak encryption mechanism based on a hard-coded key.
This could allow an attacker to guess or decrypt the password from the cyphertext.

Weakness: CWE-326 (Inadequate Encryption Strength)

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


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

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

## Is CVE-2024-54089 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-54089 is a high-severity vulnerability in Siemens APOGEE PXC Series (BACnet), published on 11 Feb 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-54089 in the wild and no public exploit code.

Affected product: Siemens APOGEE PXC Series (BACnet). 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-54089/ (Markdown: https://insights.sbomify.com/CVE-2024-54089/index.md)
```

## Sources

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

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