Raw vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:LSummary
CVE-2024-28999 is a medium-severity Race Condition (CWE-362) vulnerability in Solarwinds Solarwinds Platform. Its CVSS base score is 6.4 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-39 (Process Isolation) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The SolarWinds Platform is affected by a race condition vulnerability, tracked as CVE-2024-28999 and assigned CWE-362, that impacts the web console. The issue carries a CVSS 3.1 score of 6.4 with an attack vector of adjacent network, high attack complexity, no required privileges or user interaction, and impacts described as high on confidentiality with limited effects on integrity and availability.
An attacker positioned on an adjacent network can exploit the race condition to achieve unauthorized access or manipulation of console resources. Because the flaw requires no authentication, an adversary could potentially read sensitive data or perform limited modifications and disruptions without user assistance.
SolarWinds has published mitigation guidance in the SolarWinds Platform 2024.2 release notes and the associated security advisory on its trust center, directing customers to apply the referenced platform update.
The EPSS score remains flat at 0.0648 with no material increase since disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-26061
Vulnerability Data
The SolarWinds Platform was determined to be affected by a Race Condition Vulnerability affecting the web console.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V10.4.2V10.4.5V15.1.3V15.4.1
Mitigating Controls (NIST 800-53 r5) AI
Maintaining separate execution domains for each process structurally eliminates unintended concurrent access to the same shared resources.
Preventing unintended information transfer through shared system resources directly addresses the improper concurrent modification that defines a race condition.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require proper synchronization primitives and concurrency testing that prevent race conditions.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect race conditions, but does not prevent them at design or coding time.
Secure SDLC mandates concurrency controls and synchronization primitives that directly prevent race conditions.
Application security requirements can specify thread-safety and locking rules, but do not prescribe implementation details.
Secure architecture principles require proper synchronization and resource isolation, addressing the root cause of CWE-362.
Secure coding standards explicitly forbid unsafe concurrent access patterns and mandate atomic operations or locks.
Change management reduces introduction of concurrency bugs during updates, yet does not address the weakness itself.