A race condition vulnerability exists in the SolarWinds Platform web console. The flaw arises from improper synchronization of concurrent operations, which could allow an attacker to exploit timing issues in the web console's processing logic.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a Python proof-of-concept exploit for CVE-2024-28999, a race condition vulnerability in the SolarWinds Platform web console login page (versions 2024.1 SR 1 and earlier). The main script, CVE-2024-28999.py, prompts the user for a target host, username, and a file containing passwords. It then initiates multiple parallel login attempts using unique session IDs to exploit the race condition, aiming to brute-force valid credentials. The exploit leverages both synchronous and asynchronous HTTP requests (using requests and aiohttp) to maximize the chance of successful exploitation. The README provides usage instructions and context. No weaponized payload is included; the script is a POC for credential brute-forcing via a race condition. The main fingerprintable endpoint is the SolarWinds login page at '/Orion/Login.aspx' over HTTPS. The repository is well-structured, with clear separation between code and documentation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.