# CVE-2024-1212: Progress Kemp LoadMaster OS Command Injection

> Unauthenticated attackers can execute arbitrary system commands on LoadMaster devices via the management interface.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 18 Nov 2024 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2024
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-8vv7-j7w3-28ww

## What is CVE-2024-1212?

CVE-2024-1212 is a critical command injection vulnerability in Progress Software LoadMaster, published on 21 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unauthenticated remote attackers can access the system through the LoadMaster management interface, enabling arbitrary system command execution.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Progress Loadmaster.

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

No fix has been published for CVE-2024-1212 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 9 Dec 2024.

## Is CVE-2024-1212 being exploited?

Yes. Attackers have exploited CVE-2024-1212 in the wild since at least 18 Nov 2024.

Public exploit code:

- Unauthenticated Command Injection In Progress Kemp LoadMaster (github_poc): https://github.com/Chocapikk/CVE-2024-1212
- Kemp LoadMaster Unauthenticated Command Injection (metasploit)
- Kemp LoadMaster Local sudo privilege escalation (metasploit)
- https://github.com/r0otk3r/CVE-2024-1212 (github_poc): https://github.com/r0otk3r/CVE-2024-1212
- Progress Kemp LoadMaster - Command Injection (nuclei): http/cves/2024/CVE-2024-1212.yaml

## Other vulnerabilities in Progress Software LoadMaster

- [CVE-2014-5287](https://insights.sbomify.com/CVE-2014-5287/): Command injection in n/a (high 8.8)
- [CVE-2024-56131](https://insights.sbomify.com/CVE-2024-56131/): Improper Input Validation vulnerability of Authenticated User in Progress LoadMaster allows : OS Command Injection. (high 8.4)
- [CVE-2024-56132](https://insights.sbomify.com/CVE-2024-56132/): Improper Input Validation vulnerability of Authenticated User in Progress LoadMaster allows : OS Command Injection. (high 8.4)
- [CVE-2024-56133](https://insights.sbomify.com/CVE-2024-56133/): Improper Input Validation vulnerability of Authenticated User in Progress LoadMaster allows : OS Command Injection. (high 8.4)
- [CVE-2024-56134](https://insights.sbomify.com/CVE-2024-56134/): Improper Input Validation vulnerability of Authenticated User in Progress LoadMaster allows : OS Command Injection. (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1212 is a critical command injection vulnerability in Progress Software LoadMaster, published on 21 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-1212 in the wild since at least 18 Nov 2024.

Affected product: Progress Software LoadMaster. 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-1212/ (Markdown: https://insights.sbomify.com/CVE-2024-1212/index.md)
```

## Sources

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

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