LiveActive security incident?Get immediate response
CVE Record

CVE-2020-5405: Directory Traversal with spring-cloud-config-server

Spring Cloud Config, versions 2.2.x prior to 2.2.2, versions 2.1.x prior to 2.1.7, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead a directory traversal attack.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-5405 is a directory traversal flaw in Spring Cloud Config Server. An attacker able to send a crafted request to the server could make it serve configuration files outside the intended path. Business risk depends on whether those files contain secrets or sensitive operational settings.

Executive priority

Prioritize remediation where Config Server is internet-facing, shared across environments, or stores secrets. Treat this as a configuration confidentiality risk, not just a software version issue.

Technical view

Spring Cloud Config versions 2.2.x before 2.2.2, 2.1.x before 2.1.7, and older unsupported versions are affected in the spring-cloud-config-server module. The assigned weakness is CWE-23, directory traversal. The supplied data does not include CVSS scoring.

Likely exposure

Organizations are most exposed when Spring Cloud Config Server is reachable by untrusted users or networks and stores credentials, service endpoints, tokens, or environment-specific configuration. Internal-only deployments still matter if broad internal access exists.

Exploitation context

The supplied sources do not show active exploitation, and the CVE is not listed as KEV in the provided bundle. The vulnerability is request-driven and depends on an attacker reaching the Config Server interface.

Researcher notes

Evidence is limited to CVE and vendor references. No CVSS vector, exploit confirmation, or detailed workaround is included in the supplied bundle. Validate exposure by version, module use, network reachability, and sensitivity of served configuration data.

Mitigation direction

  • Upgrade 2.2.x deployments to 2.2.2 or later.
  • Upgrade 2.1.x deployments to 2.1.7 or later.
  • Replace older unsupported Spring Cloud Config versions.
  • Restrict Config Server access to trusted networks and authenticated clients.
  • Review vendor guidance before applying compensating controls.

Validation and detection

  • Inventory services running spring-cloud-config-server.
  • Confirm deployed Spring Cloud Config versions against affected ranges.
  • Check whether Config Server endpoints are reachable externally or broadly internally.
  • Review exposed configuration repositories for secrets or sensitive settings.
  • Verify upgrades are covered by regression tests before deployment.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-23: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-5405 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Spring by VMwareSpring Cloud Config2.2, 2.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-23 · source CWE mapping

Relative Path Traversal

Relative Path Traversal represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.