How severe is CVE-2019-3799?

CVE-2019-3799 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-3799?

CVE-2019-3799 affects the following packages: org.springframework.cloud:spring-cloud-config-server (Maven), org.springframework.cloud:spring-cloud-config-server (Maven), org.springframework.cloud:spring-cloud-config-server (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-3799?

Update org.springframework.cloud:spring-cloud-config-server to 1.4.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-3799 is resolved across your whole dependency graph.

How do I detect CVE-2019-3799 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.cloud:spring-cloud-config-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2019-3799 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2019-3799?

O3 pinpoints whether CVE-2019-3799 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2019-3799 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2019-3799, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is CVE-2019-3799?

CVE-2019-3799 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2019-3799?

A Nuclei detection template exists for CVE-2019-3799, meaning automated scanners can fingerprint it. A Metasploit module references CVE-2019-3799, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2019-3799 published, and has it been updated?

CVE-2019-3799 was published on May 6, 2019 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

CVE-2019-3799

MEDIUM

CVE-2019-3799 is a medium-severity (CVSS 6.5) Path Traversal vulnerability in org.springframework.cloud:spring-cloud-config-server. 5 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2019-3799 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Path Traversal in Spring Cloud Config

Also known asGHSA-4x49-w62v-76q7

Published

May 6, 2019

Updated

Jul 8, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

5 known

Blast Radius

3 pkgs affected

☕org.springframework.cloud:spring-cloud-config-server☕org.springframework.cloud:spring-cloud-config-server☕org.springframework.cloud:spring-cloud-config-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.cloud:spring-cloud-config-server`	all versions	1.4.6
☕Maven	`org.springframework.cloud:spring-cloud-config-server`	≥ 2.0.0&&< 2.0.4	2.0.4
☕Maven	`org.springframework.cloud:spring-cloud-config-server`	≥ 2.1.0&&< 2.1.2	2.1.2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-46772webappsjava

Spring Cloud Config 2.1.x - Path Traversal (Metasploit)

by Dhiraj Mishra · Apr 30, 2019

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.cloud:spring-cloud-config-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.springframework.cloud:spring-cloud-config-server to 1.4.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-3799 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2019-3799 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2019-3799. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-3799 in your dependencies?

O3 detects CVE-2019-3799 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10

CVSS v3 base score

Vector breakdown

AV:Attack Vector

Network

AC:Attack Complexity

Low

PR:Privileges Required

None

UI:User Interaction