CVE-2019-3799: Directory Traversal with spring-cloud-config-server
Noroxi assessment
Priority: This week (action score 60/100)
- A ready-made attack module is public (Metasploit, Nuclei); exploiting it takes no special expertise.
- A ready-made attack tool exists and the flaw can be exploited over the network without an account, so priority is at least “This week”.
- Probability of exploitation in the next 30 days: 85.2% (FIRST EPSS); higher than 99.7% of all records.
- 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.
- Fixed version: org.springframework.cloud:spring-cloud-config-server (Maven) 2.0.4, 2.1.2, 1.4.6.
Don’t wait for the next maintenance window. Upgrade to org.springframework.cloud:spring-cloud-config-server (Maven) 2.0.4, 2.1.2, 1.4.6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 6, 2019
- Updated
- Jun 16, 2026
- EPSS
- 85.2% · 99th percentile
- CWE
- CWE-22
Report tools
Action score
60
Don’t wait for the next maintenance window.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 26 / 30 · 85.2%
- Ready-made attack tool
- 8 / 60 · floor: at least 60
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Weaponized exploit exists
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| vmware | spring cloud config | cpe:2.3:a:vmware:spring_cloud_config |
| oracle | communications cloud native core policy | cpe:2.3:a:oracle:communications_cloud_native_core_policy |
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
Affected versions · NVD (4)
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
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.springframework.cloud:spring-cloud-config-server | from 2.0.0 · before 2.0.4 | 2.0.4 |
| Maven | org.springframework.cloud:spring-cloud-config-server | from 2.1.0 · before 2.1.2 | 2.1.2 |
| Maven | org.springframework.cloud:spring-cloud-config-server | before 1.4.6 | 1.4.6 |
Same product
vmware: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-5410Directory Traversal with spring-cloud-config-serverKEV89Now
- CVE-2020-5405Directory Traversal with spring-cloud-config-server47Plan
- CVE-2026-47837Spring Cloud Config Server Monitor Endpoint Does Not Validate Webhook Requests39Monitor
Published before and after this one in the same product
- Later →CVE-2023-20859Mar 23, 2023 · In Spring Vault, versions 3.0.x prior to 3.0.2 and versions 2.3.x prior to 2.3.3 and older versions, an application is vulnerable to…22Monitor
- Later →CVE-2026-22739Mar 23, 2026 · Spring Cloud Config Profile Substitution Can Allow Unintended Access To Files And Enable SSRF Attacks34Monitor
- Later →CVE-2026-40981May 7, 2026 · When using Google Secrets Manager as a backend for the Spring Cloud Config server a client can craft a request to the config server…30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.springframework.cloud:spring-cloud-config-server | 1.4.6 | Package registry (OSV) |
| Maven:org.springframework.cloud:spring-cloud-config-server | 2.0.4 | Package registry (OSV) |
| Maven:org.springframework.cloud:spring-cloud-config-server | 2.1.2 | Package 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.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | webapps | 2019-04-30 |
| Exploit-DB entry | webapps | 2019-04-30 |
| Metasploit module | auxiliary/scanner/http/springcloud_traversalSpring Cloud Config Server Directory Traversalauxiliary | 2019-04-17 |
| Nuclei detection template | Nuclei template CVE-2019-3799 | — |
| Proof-of-concept repository on GitHub | stars:31 | 2019-04-17 |
| Proof-of-concept repository on GitHub | stars:0 | 2022-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.
- First PoC-20 d
- Metasploit-20 d
- Published
- TodayNov 16, 2026+2751 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
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.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.