Threats / Progress / CVE-2024-1212
CVE-2024-1212
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Progress Kemp LoadMaster vulnerability
Progress Kemp LoadMaster contains an OS command injection vulnerability allowing unauthenticated remote attackers to execute arbitrary system commands through the management interface.
Verdict
Today item — known-exploited.
An unauthenticated remote attacker can inject OS commands via the LoadMaster management interface to achieve arbitrary code execution on affected systems. The high EPSS score and active exploitation indicate immediate risk to exposed instances.
CISA KEV Yes · 2024-11-185EPSS 0.95388 (verify live)6Exploit Weaponized · public PoC7CVSS 103CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
529 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-11-18).
Probability (EPSS)
EPSS 0.95388 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 10 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) · Affected: Progress, Kemp LoadMaster. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-78 OS Command Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 271 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify the LoadMaster management interface as publicly accessible and craft a malicious input containing OS command injection payloads.
Business
The organization's load balancer, a critical network appliance, becomes a pivot point for lateral movement into protected infrastructure.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary system commands with the privileges of the LoadMaster process to establish persistent access or exfiltrate configuration data.
Business
Attackers gain control of traffic routing and SSL termination, enabling man-in-the-middle attacks against all downstream services.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage the compromised LoadMaster to deploy malware, establish reverse shells, or modify firewall rules to enable further network penetration.
Business
The organization faces potential data breach, service disruption, and loss of visibility over network security controls.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by ProgressSoftwareCNA
Credited with finding itRhino Security Labsfinder