What is CVE-2024-28075?
The SolarWinds Access Rights Manager was susceptible to Remote Code Execution Vulnerability. This vulnerability allows an authenticated user to abuse SolarWinds service resulting in remote code execution. We thank Trend Micro Zero Day Initiative (ZDI) for its ongoing partnership in coordinating with SolarWinds on responsible disclosure of this and other potential vulnerabilities.
The record classifies CVE-2024-28075 under weakness class CWE-502. Its CVSS v3 base vector states that the flaw is reachable from an adjacent network, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 919 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 9 — CRITICAL
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - EPSS (FIRST)
- 78.0% probability of exploitation in the next 30 days, higher than 99.5% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 10/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2024-05-14
Is CVE-2024-28075 being exploited?
Weaponised exploit code for CVE-2024-28075 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 38 in the Threadlinqs vulnerability feed.
- trickest/cve (trickest)
Affected products and versions
- Solarwinds: Access Rights Manager
How to fix CVE-2024-28075
The record marks a vendor fix as available for CVE-2024-28075. Patch reference: https://www.solarwinds.com/trust-center/security-advisories/cve-2024-28075. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.
Threat activity tracking CVE-2024-28075
1 tracked threat in the Threadlinqs corpus references CVE-2024-28075, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories.