basicsecurity.net
Proof, not just disclosure.
Threats / VMware Tanzu / CVE-2020-5410
CVE-2020-5410 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

VMware Tanzu Spring Cloud Configuration (Config) Server vulnerability

Spring Cloud Configuration Server contains a path traversal vulnerability allowing unauthorized access to arbitrary configuration files on affected systems.

Verdict

Today item — known-exploited.

A path traversal flaw in Spring Cloud Configuration Server enables attackers to bypass access controls and retrieve sensitive configuration data, credentials, and application secrets stored outside intended directories.

CISA KEV Yes · 2022-03-253EPSS 0.95586 (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
8 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 2022-03-25).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.95586 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: VMware Tanzu, Spring Cloud Configuration (Config) Server. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-23 Relative 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-23 · Relative 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 malicious requests with path traversal sequences to navigate the file system and access configuration files outside the designated config directory.
Business
Sensitive application credentials, database passwords, and API keys are exposed to unauthorized parties.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I extract exposed credentials and secrets from retrieved configuration files to gain access to backend systems and databases.
Business
Attackers obtain valid authentication material enabling lateral movement and unauthorized access to critical infrastructure.
3

Lateral reach — past segmentation narrative 3

Attacker
I use obtained credentials to access databases, internal services, and cloud resources tied to the compromised application.
Business
Data breach scope expands beyond the configuration server to include customer data, intellectual property, and operational systems.
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)
  • 8 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by pivotal (CNA)
  • 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.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by pivotalCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.