CVE-2024-2448
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 · uneditedAn OS command injection vulnerability has been identified in LoadMaster. An authenticated UI user with any permission settings may be able to inject commands into a UI component using a shell command resulting in OS command injection.
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 confidenceOS command injection vulnerability in Kemp LoadMaster allows any authenticated UI user - regardless of permission level - to inject arbitrary shell commands through a UI component. This enables complete compromise of the LoadMaster device operating system.
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>= 7.2.49.0, < 7.2.54.9>= 7.2.55.0, < 7.2.59.3= 7.1.35.10= 7.2.48.10CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify LoadMaster versionAccess the LoadMaster administration interface and navigate to the System Configuration > System Administration > Update/Reboot section, or check the login banner which typically displays the version on the main login page. Alternatively, use the API endpoint or check the installed package via command line if available.Affected if The installed version falls within: 7.2.49.0 to 7.2.54.8, 7.2.55.0 to 7.2.59.2, 7.1.35.10, or 7.2.48.10.
-
Verify UI accessibilityDetermine if the LoadMaster web interface (typically ports 443 or 8443) is exposed to untrusted networks or the internet. Check network firewall rules, access control lists, or perform a port scan of the LoadMaster IP address.Affected if The UI is accessible from untrusted networks or the internet, increasing the attack surface for credentialed attackers.
-
Review user accountsAccess the LoadMaster UI and navigate to Users & Security > User Management to enumerate all configured user accounts. Check for any unauthorized, unexpected, or newly created accounts.Affected if There are user accounts that were not created by legitimate administrators, or if the total number of accounts exceeds expectations.
-
Audit recent user login activityCheck LoadMaster logs for recent authentication events, particularly successful logins from unfamiliar IP addresses or at unusual times. Access logs via the UI under System Configuration > Logging > Log Viewer, or review system logs.Affected if There are successful authentications from IP addresses not belonging to known administrators, or authentication patterns indicating compromise.
-
Inspect for command injection indicatorsReview LoadMaster system logs, access logs, and audit logs for patterns indicative of command injection attempts, such as shell metacharacters (;, |, &, $ , `, etc.) in UI parameters, or unexpected system commands being executed.Affected if Log entries contain suspicious command patterns or indicate execution of unexpected system commands initiated through the UI.
You are affected if your LoadMaster version is 7.1.35.10, 7.2.48.10, or within 7.2.49.0-7.2.54.8 or 7.2.55.0-7.2.59.2 AND the UI is accessible to untrusted authenticated users.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data7.2.54.97.2.59.3
Restrict LoadMaster UI access to trusted administrators only; monitor for unauthorized access; apply vendor security patches when available; network-segment LoadMaster devices to limit attack surface.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2448 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-2448 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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