# CVE-2024-12372: Rockwell Automation PowerMonitor™ 1000 Denial of Service

> Heap memory corruption in Rockwell PowerMonitor 1000 allows remote attackers to execute code or cause denial of service.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 18 Dec 2024
- **Updated:** 18 Dec 2024
- **Also known as:** GHSA-p988-wjfg-fj9j

## What is CVE-2024-12372?

CVE-2024-12372 is a critical memory corruption vulnerability in Rockwell Automation PM1k 1408-BC3A-485, published on 18 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A denial-of-service and possible remote code execution vulnerability exists in the Rockwell Automation Power Monitor 1000. The vulnerability results in corruption of the heap memory which may compromise the integrity of the system, potentially allowing for remote code execution or a denial-of-service attack.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2024-12372 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-12372 is a critical memory corruption vulnerability in Rockwell Automation PM1k 1408-BC3A-485, published on 18 Dec 2024. 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-12372 in the wild and no public exploit code.

Affected product: Rockwell Automation PM1k 1408-BC3A-485. 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-12372/ (Markdown: https://insights.sbomify.com/CVE-2024-12372/index.md)
```

## Sources

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

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