dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 9 Dec 2024.
LoadmasterOperating system · Progress

CVE-2024-1212

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-21
Fix available
A fix is available. Upgrade to 7.2.48.10 / 7.2.54.8 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a critical vulnerability in Kemp LoadMaster load balancer's management interface that allows unauthenticated remote attackers to bypass authentication and execute arbitrary system commands. The lack of authentication requirement combined with command execution capability makes this immediately exploitable and severely dangerous.

MitigationImmediately restrict network access to the LoadMaster management interface (e.g., via firewall rules, access control lists, or disabling external management access) and monitor for indicators of compromise. Apply vendor patches as soon as they become available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LoadmasterOperating system
Affected:>= 7.2.48.1, < 7.2.48.10>= 7.2.54.0, < 7.2.54.8>= 7.2.55.0, < 7.2.59.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the LoadMaster product and version
    Access the LoadMaster management interface and check the version information typically displayed in the About or System Status section of the web console, or run 'lmutil --ver' from the command line if available
    Affected if The installed version falls within any of these ranges: >= 7.2.48.1 and < 7.2.48.10, OR >= 7.2.54.0 and < 7.2.54.8, OR >= 7.2.55.0 and < 7.2.59.2
  2. Determine if the management interface is network accessible
    Verify network exposure by checking the LoadMaster network configuration settings for the management interface (typically ports 443 or 8443) and determine if it is bound to external-facing interfaces
    Affected if The LoadMaster management interface is reachable from untrusted or external networks without VPN filtering
  3. Confirm the management interface responds to requests
    Attempt to access the LoadMaster management login page from the network perspective you are evaluating (e.g., curl or browser request to https://<host>/)
    Affected if The management interface is accessible and does not require authentication credentials before processing requests (the vulnerability allows unauthenticated command execution)

You are affected if you are running a Progress LoadMaster version within the vulnerable ranges AND the management interface is accessible from untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.2.48.10 / 7.2.54.8 / 7.2.59.2 or later
Fixed in 7.2.48.107.2.54.87.2.59.2
Interim mitigation

Immediately restrict network access to the LoadMaster management interface (e.g., via firewall rules, access control lists, or disabling external management access) and monitor for indicators of compromise. Apply vendor patches as soon as they become available.

Recommended fix High confidence

Upgrade to version 7.2.48.10 (if on 7.2.48.x), or 7.2.54.8 (if on 7.2.54.x-7.2.55.x), or 7.2.59.2 (if on 7.2.55.0-7.2.59.1)

  1. 1. Identify current LoadMaster version via the management interface (Help > About) or via CLI command 'show version'
  2. 2. Based on current version, determine the appropriate fixed version to upgrade to (see upgrade_path)
  3. 3. Create a full backup of the LoadMaster configuration via the management interface (Properties > Backup/Restore)
  4. 4. Download the appropriate fixed LoadMaster version from Kemp Technologies official support portal
  5. 5. Apply the upgrade via the management interface (Properties > Update) or via CLI following Kemp's documented upgrade procedure
  6. 6. After upgrade completes, verify the new version matches the fixed release
  7. 7. Confirm the vulnerability is resolved by verifying the management interface is no longer exposed to unauthenticated command injection
Caveat Standard LoadMaster upgrade - ensure configuration backup before proceeding; test in staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Loadmaster Exploited in the wild — priority engagement
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,940
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1212 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1212 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data