CVE-2019-3799

MEDIUMNVD 6.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 85% probability of exploitation within the next 30 days (top 0.3% of all CVEs). NVD baseline CVSS 6.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Trending — 3 sources updated this weekWeaponized
6.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 85%
CISA-KEV: Not listedEPSS: 85%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
9.0(high)
EG Risk
79(Track)
EG Risk 79/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation85% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.7%
KEV
Not listed

Published

May 6, 2019

Last Modified

November 21, 2024

References (4)

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.springframework.cloud:spring-cloud-config-server2.1.0.RELEASE, 2.1.1.RELEASE2.1.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 01:45 UTCEG score recompute
  2. 2026-07-22 22:25 UTCEG score recompute
  3. 2026-07-22 14:05 UTCEPSS rescore
  4. 2026-07-21 15:22 UTCEPSS rescore
  5. 2026-07-21 15:22 UTCEPSS rescore
  6. 2026-07-20 17:02 UTCOSV refresh
  7. 2026-07-19 02:26 UTCEPSS rescore
  8. 2026-07-19 02:26 UTCEPSS rescore
  9. 2026-07-15 16:55 UTCEPSS rescore
  10. 2026-07-13 06:10 UTCEPSS rescore
  11. 2026-07-13 06:10 UTCEPSS rescore
  12. 2026-07-11 08:24 UTCEPSS rescore
  13. 2026-07-11 08:24 UTCEPSS rescore
  14. 2026-07-06 02:20 UTCEPSS rescore
  15. 2026-07-06 02:20 UTCEPSS rescore
  16. 2026-07-03 11:56 UTCOSV refresh
  17. 2026-06-30 23:20 UTCEPSS rescore
  18. 2026-06-29 14:03 UTCEPSS rescore
  19. 2026-06-28 04:54 UTCEPSS rescore
  20. 2026-06-28 04:54 UTCEPSS rescore
  21. 2026-06-24 14:03 UTCEPSS rescore
  22. 2026-06-24 14:03 UTCEPSS rescore
  23. 2026-06-23 21:31 UTCEPSS rescore
  24. 2026-06-23 21:31 UTCEPSS rescore
  25. 2026-06-21 01:57 UTCEPSS rescore
Show 21 more
  1. 2026-06-21 01:57 UTCEPSS rescore
  2. 2026-06-17 17:50 UTCEPSS rescore
  3. 2026-06-16 17:50 UTCEPSS rescore
  4. 2026-06-15 17:46 UTCEPSS rescore
  5. 2026-06-15 02:13 UTCOSV refresh
  6. 2026-06-14 23:15 UTCEPSS rescore
  7. 2026-06-14 23:15 UTCEPSS rescore
  8. 2026-06-13 22:58 UTCEPSS rescore
  9. 2026-06-10 22:16 UTCEPSS rescore
  10. 2026-06-10 22:16 UTCEPSS rescore
  11. 2026-06-06 13:45 UTCEPSS rescore
  12. 2026-06-06 13:45 UTCEPSS rescore
  13. 2026-06-05 22:45 UTCEPSS rescore
  14. 2026-05-31 22:29 UTCEPSS rescore
  15. 2026-05-31 22:29 UTCEPSS rescore
  16. 2026-05-29 13:42 UTCEPSS rescore
  17. 2026-05-28 13:43 UTCEPSS rescore
  18. 2026-05-28 13:43 UTCEPSS rescore
  19. 2026-05-27 19:53 UTCEG score recompute
  20. 2026-05-26 13:42 UTCEPSS rescore
  21. 2026-05-24 16:47 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-46772
    First seen Apr 30, 2019

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

    Open source ↗
  • GitHub PoCmpgn/CVE-2019-3799
    First seen Apr 17, 2019

    CVE-2019-3799 - Spring Cloud Config Server: Directory Traversal < 2.1.2, 2.0.4, 1.4.6

    Open source ↗
  • Metasploitauxiliary/scanner/http/springcloud_traversal✓ verified
    First seen Apr 17, 2019

    Spring Cloud Config Server Directory Traversal

    Open source ↗
  • Nucleihttp/cves/2019/CVE-2019-3799.yaml
    First seen Jan 1, 2019

    Spring Cloud Config Server - Local File Inclusion

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-3799?
CVE-2019-3799 is a medium vulnerability published on May 6, 2019. 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…
When was CVE-2019-3799 disclosed?
CVE-2019-3799 was first published in the National Vulnerability Database on May 6, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-3799 actively exploited?
CVE-2019-3799 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-3799?
CVE-2019-3799 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2019-3799?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-3799, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-3799

Explore →

Is Your Infrastructure Affected by CVE-2019-3799?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs