LoadMaster Hardcoded SSH Key
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Progress Software Corporation LoadMaster 7.2.48.12, 7.2.54.10, 7.2.59.4.
Low priority for now. Upgrade to Progress Software Corporation LoadMaster 7.2.48.12, 7.2.54.10, 7.2.59.4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Unauthenticated attackers can perform actions, using SSH private keys, by knowing the IP address and having access to the same network of one of the machines in the HA or Cluster group. This vulnerability has been closed by enhancing LoadMaster partner communications to require a shared secret that must be exchanged between the partners before communication can proceed.
- Published
- May 2, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 30th percentile
- CWE
- CWE-798
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · ProgressSoftware
- 7.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| progress | loadmaster | cpe:2.3:a:progress:loadmaster |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- progress loadmasterbefore 7.2.48.11
- progress loadmaster7.2.49.0 and later · before 7.2.54.10
- progress loadmaster7.2.55.0 and later · before 7.2.59.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (ProgressSoftware). Independent of NVD's CPE analysis and usually ahead of it.
Progress Software Corporation LoadMaster
- LoadMaster 7.2.55.0 (GA) and later · before 7.2.59.4affected · semver
- LoadMaster 7.2.49.0 (LTSF) and later · before 7.2.54.10affected · semver
- LoadMaster 7.2.48.11 (LTS) and later · before 7.2.48.12affected · semver
Same product
progress: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-1212LoadMaster Pre-Authenticated OS Command InjectionKEV98Now
- CVE-2024-2448LoadMaster Command Injection Vulnerability52Plan
- CVE-2024-8755Improper Input Validation vulnerability of Authenticated User in Progress LoadMaster allows : OS Command Injection.39Monitor
- CVE-2014-5287A Bash script injection vulnerability exists in Kemp Load Master 7.1-16 and earlier due to a failure to sanitize input in the Web User Inter37Monitor
- CVE-2024-2449LoadMaster Cross-Site Request Forgery (CSRF)34Monitor
- CVE-2024-3543LoadMaster Reversible Password Encryption Algorithm30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Progress Software Corporation LoadMaster | 7.2.48.12 | Vendor (CNA) |
| Progress Software Corporation LoadMaster | 7.2.54.10 | Vendor (CNA) |
| Progress Software Corporation LoadMaster | 7.2.59.4 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-798 · Use of Hard-coded CredentialsCVSS vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
For convenience in support or manufacturing, an account that is identical on every device is embedded in the software. Credentials learned from one device work on all of them.
The bug in code
The whole CWE-798 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const SUPPORT_USER = "support";const SUPPORT_PASS = "hardcoded-password";Fixed
const creds = await provisioning.deviceCredentials(deviceId);if (creds.mustRotate) await forcePasswordChange(deviceId);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.