Skip to content
Noroxi
CVE-2019-3799· NVD / CVE Program· CNA dell

Directory Traversal with spring-cloud-config-server

Spring Cloud Config, versions 2.1.x prior to 2.1.2, versions 2.0.x prior to 2.0.4, and versions 1.4.x prior to 1.4.6, 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.

MediumCVSS 6.5 · v3.1—Weaponized Fix available
Published
May 6, 2019
Updated
Jun 16, 2026
EPSS
85.3% · 100th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

52

Plan

Add it to your regular patch cycle.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
26 / 30 · 85.3%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
vmwarespring cloud config
oraclecommunications cloud native core policy

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • oracle communications cloud native core policy1.15.0
  • vmware spring cloud config1.4.0 and later · before 1.4.6
  • vmware spring cloud config2.0.0 and later · before 2.0.4
  • vmware spring cloud config2.1.0 and later · before 2.1.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (dell). Independent of NVD's CPE analysis and usually ahead of it.

  • Spring Spring Cloud Config

    • 2.0 and later · before v2.0.4.RELEASEaffected
    • 1.4 and later · before v1.4.6.RELEASEaffected
    • 2.1 and later · before v2.1.2.RELEASEaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.springframework.cloud:spring-cloud-config-serverfrom 2.0.0 · before 2.0.42.0.4
Mavenorg.springframework.cloud:spring-cloud-config-serverfrom 2.1.0 · before 2.1.22.1.2
Mavenorg.springframework.cloud:spring-cloud-config-serverbefore 1.4.61.4.6

Same product

vmware: all records

Other highest-scoring records for the same primary product.

  • CVE-2020-5410Directory Traversal with spring-cloud-config-serverKEV
    89Now
  • CVE-2020-5405Directory Traversal with spring-cloud-config-server
    47Plan
  • CVE-2026-47837Spring Cloud Config Server Monitor Endpoint Does Not Validate Webhook Requests
    39Monitor
  • CVE-2026-40982Spring Cloud Config allows applications to serve arbitrary text and binary files through the spring-cloud-config-server module.
    36Monitor
  • CVE-2026-22739Spring Cloud Config Profile Substitution Can Allow Unintended Access To Files And Enable SSRF Attacks
    34Monitor
  • CVE-2026-47836Spring Cloud Config Server Susceptible To TOCTOU Attack When Using SVN
    32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:org.springframework.cloud:spring-cloud-config-server1.4.6Package registry (OSV)
Maven:org.springframework.cloud:spring-cloud-config-server2.0.4Package registry (OSV)
Maven:org.springframework.cloud:spring-cloud-config-server2.1.2Package registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Metasploit module ×1
  • Exploit-DB entry ×2
  • Nuclei detection template ×1
  • Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entrywebapps2019-04-30
Exploit-DB entrywebapps2019-04-30
Metasploit moduleauxiliary/scanner/http/springcloud_traversalSpring Cloud Config Server Directory Traversalauxiliary2019-04-17
Nuclei detection templateNuclei template CVE-2019-3799 —
Proof-of-concept repository on GitHubstars:312019-04-17
Proof-of-concept repository on GitHubstars:02022-04-07

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-20 d
  2. Metasploit-20 d
  3. Published
  4. TodaySep 30, 2026+2704 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records