basicsecurity.net
Proof, not just disclosure.
Threats / SolarWinds / CVE-2024-28995
CVE-2024-28995 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

SolarWinds Serv-U vulnerability

SolarWinds Serv-U contains a path traversal vulnerability (CWE-22) allowing attackers to read sensitive files on affected systems. The vulnerability is actively exploited in the wild.

Verdict

Today item — known-exploited.

A path traversal flaw in SolarWinds Serv-U enables unauthorized file access on vulnerable hosts. With an EPSS score of 0.94, this vulnerability poses significant risk and is currently being exploited by threat actors.

CISA KEV Yes · 2024-07-173EPSS 0.99614 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
672 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-07-17).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.99614 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: SolarWinds, Serv-U. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-22 Path Traversal — weakness family: Path traversal / file.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-22 · Path TraversalPath traversal / file
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a request using path traversal sequences to escape the intended directory and access arbitrary files on the server.
Business
Sensitive configuration files, credentials, or application data become exposed to unauthorized parties.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I extract credentials or authentication tokens from accessible files to escalate privileges or move laterally within the environment.
Business
Compromised credentials enable further system compromise and potential data exfiltration or operational disruption.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Public PoC available (VulnCheck)
  • 672 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by SolarWinds (CNA)
  • Named finder/reporter credit (CVE.org)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • Disclosure & credit2
    Catalogued by SolarWindsCNA
    Credited with finding itHussein Daherfinder