LoadMaster Cross-Site Request Forgery (CSRF)
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.2.59.3 ( LoadMaster GA), 7.2.54.9 ( LoadMaster LTSF), 7.2.48.11 (LoadMaster LTS), 7.1.35.11 (LoadMaster MT)
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A cross-site request forgery vulnerability has been identified in LoadMaster. It is possible for a malicious actor, who has prior knowledge of the IP or hostname of a specific LoadMaster, to direct an authenticated LoadMaster administrator to a third-party site. In such a scenario, the CSRF payload hosted on the malicious site would execute HTTP transactions on behalf of the LoadMaster administrator.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- Progress Software LoadMaster
From 7.2.55.0 · fixed in 7.2.59.3 ( LoadMaster GA); From 7.2.49.0 · fixed in 7.2.54.9 ( LoadMaster LTSF); From 7.2.48.10 · fixed in 7.2.48.11 (LoadMaster LTS); From 7.1.35.10 · fixed in 7.1.35.11 (LoadMaster MT)