CVE-2024-8755
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 · uneditedImproper Input Validation vulnerability of Authenticated User in Progress LoadMaster allows : OS Command Injection.This issue affects: Product Affected Versions LoadMaster From 7.2.55.0 to 7.2.60.1 (inclusive) From 7.2.49.0 to 7.2.54.12 (inclusive) 7.2.48.12 and all prior versions Multi-Tenant Hypervisor 7.1.35.12 and all prior versions ECS All prior versions to 7.2.60.1 (inclusive)
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 · high confidenceImproper input validation in Progress LoadMaster allows authenticated users to inject OS commands, enabling complete system compromise. This is a command injection vulnerability requiring valid authentication, but with CVSS 9.8 indicating trivial exploitability once credentials are obtained.
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.48.12>= 7.2.49.0, <= 7.2.54.12>= 7.2.55.0, < 7.2.61.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Progress LoadMaster is deployedLook for the LoadMaster web management interface (typically on port 443/8443), or check running processes/services for LoadMaster-related components.Affected if LoadMaster is found running in the environment
-
Determine the installed LoadMaster versionLog into the LoadMaster web UI and navigate to System Configuration > System Administration > System Debug > Version, or use the 'lmutil' command-line tool if available. Compare the version number against the affected ranges.Affected if The installed version is <= 7.2.48.12, OR between 7.2.49.0 and 7.2.54.12 inclusive, OR between 7.2.55.0 and 7.2.60.0 inclusive (anything below 7.2.61.0)
-
Verify management interface network exposureCheck firewall rules, network ACLs, or cloud security groups to determine if the LoadMaster management interface (ports 443, 8443) is accessible from untrusted networks or the internet.Affected if The management interface is exposed to the internet or untrusted internal networks
-
Confirm authentication requirementsReview access controls and confirm that LoadMaster administrative accounts use strong, unique passwords and are not using default credentials.Affected if Weak, default, or shared administrative credentials are in use, or if the account lockout policy is not enforced
The environment is affected if LoadMaster is running with a version below 7.2.61.0 and the management interface is accessible to attackers who could obtain valid credentials.
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.
dbcve · scoped7.2.61.0
Upgrade LoadMaster, Multi-Tenant Hypervisor, and ECS to vendor-provided patched versions. As immediate workarounds, limit administrative access to trusted personnel only and restrict network exposure to the management interface.
LoadMaster 7.2.61.0 or later (for Multi-Tenant Hypervisor and ECS, upgrade to the version that supersedes 7.1.35.12 and 7.2.60.1 respectively)
- 1. Identify the current LoadMaster version by navigating to the LoadMaster User Interface > Help & Info > System Overview
- 2. Download LoadMaster version 7.2.61.0 or later from the Kemp Technologies support portal at support.kemptechnologies.com
- 3. Review the LoadMaster upgrade documentation for your deployment type (物理机/虚拟机/云)
- 4. Create a full backup of the current LoadMaster configuration before upgrading
- 5. Schedule a maintenance window as the upgrade may require a brief service interruption
- 6. Apply the upgrade by uploading the LoadMaster update through the web interface (LoadMaster User Interface > Updates > Install Update) or using the command line if preferred
- 7. After upgrade completes, verify the new version is 7.2.61.0 or later by checking Help & Info > System Overview
- 8. Confirm the LoadMaster services are functioning correctly and test critical workflows
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8755 — 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-8755 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