CVE-2024-6658
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.0 (inclusive) From 7.2.49.0 to 7.2.54.11 (inclusive) 7.2.48.12 and all prior versions Multi-Tenant Hypervisor 7.1.35.11 and all prior versions ECS All prior versions to 7.2.60.0 (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 confidenceAuthenticated OS command injection vulnerability in Progress LoadMaster due to improper input validation. An authenticated user can inject malicious OS commands through unsanitized input fields. Affects LoadMaster (versions 7.2.48.12 through 7.2.60.0), Multi-Tenant Hypervisor (7.1.35.11 and prior), and ECS (through 7.2.60.0).
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.1.35.12<= 7.2.48.12>= 7.2.49.0, < 7.2.54.12>= 7.2.55.0, < 7.2.60.1CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/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 product variant and versionAccess the LoadMaster administration interface and navigate to Help > About, or run 'lmutil -v' via SSH if available. Alternatively, check the raw API response at /api/v1/server/info or review the banner on the login page.Affected if The version falls within any of these ranges: Multi-Tenant < 7.1.35.12, LoadMaster <= 7.2.48.12, 7.2.49.0 to < 7.2.54.12, or 7.2.55.0 to < 7.2.60.1
-
Verify web interface is accessibleConfirm the LoadMaster web management interface (typically ports 443 or 8443) is reachable from your network. Check firewall rules and external exposure using a port scan or by attempting to access the URL.Affected if The web interface is exposed beyond trusted admin networks, increasing attack surface for authenticated command injection.
-
Review user accounts with administrative privilegesNavigate to Users > Manage Users in the LoadMaster UI, or query /api/v1/user/list via API. Identify all accounts with Administrative or Operator roles.Affected if Multiple user accounts exist with admin/operator access, any of which could be compromised to exploit this vulnerability.
-
Inspect audit and access logs for suspicious command executionCheck LoadMaster logs at /var/log/httperror or via the UI at Logs > Access Logs. Look for unusual API calls, especially to endpoints that accept shell commands or for patterns like semicolons, pipes, or backticks in input fields.Affected if Logs show command injection patterns or unexpected command executions that deviate from normal administrative operations.
-
Check for any unauthorized configuration changesReview the LoadMaster configuration for any unexpected Virtual Services, custom headers, or modified system parameters. Compare current configuration against known-good baselines if available.Affected if Configurations contain unexpected modifications, especially to system-level parameters that could indicate successful exploitation.
A user is affected if their LoadMaster version matches any of the vulnerable ranges AND the web interface is accessible to authenticated users, regardless of network location.
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.1.35.127.2.54.127.2.60.1
Apply vendor patches/upgrade to a patched version. Prior to patching, restrict administrative access to trusted users only and implement additional logging/monitoring for suspicious command execution.
Multi Tenant Loadmaster: 7.1.35.12 | Loadmaster: 7.2.54.12 or 7.2.60.1
- 1. Identify the currently installed LoadMaster product and version using the web interface or CLI
- 2. For Multi Tenant Loadmaster: upgrade to version 7.1.35.12 or later
- 3. For Loadmaster: if currently on 7.2.48.12 or prior, or 7.2.49.0-7.2.54.11, upgrade to 7.2.54.12 or later; if currently on 7.2.55.0-7.2.60.0, upgrade to 7.2.60.1 or later
- 4. Download the update from support.kemptechnologies.com
- 5. Apply the update following standard LoadMaster upgrade procedures
- 6. Verify the upgrade was successful and the new version is running
- 7. Confirm the vulnerability is resolved by checking the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.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 $10,496.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6658 — 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-6658 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