# CVE-2019-3799 — Spring Cloud Config

> As of 2024-09-17, CVE-2019-3799 is a MEDIUM-severity vulnerability in Spring Cloud Config, CVSS v3.1 6.5, EPSS 85.2% (99.7th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2019-3799 as of 2024-09-17; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2024-09-17

## What is CVE-2019-3799?

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.

The record classifies CVE-2019-3799 under weakness class [CWE-22](https://intel.threadlinqs.com/cwe/CWE-22). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs a user to take an action first, and has high impact on confidentiality. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 2754 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 6.5 — MEDIUM (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **EPSS (FIRST):** 85.2% probability of exploitation in the next 30 days, higher than 99.7% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 9.7/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2019-05-06

## Is CVE-2019-3799 being exploited?

Weaponised exploit code for CVE-2019-3799 is publicly available. 3 public proof-of-concept repositories are tracked for this identifier. A ProjectDiscovery Nuclei detection template exists (`http/cves/2019/CVE-2019-3799.yaml`).

- [mpgn/CVE-2019-3799](https://github.com/mpgn/CVE-2019-3799) (github)
- [Corgizz/SpringCloud](https://github.com/Corgizz/SpringCloud) (github)
- [trickest/cve](https://github.com/trickest/cve/blob/main/2019/CVE-2019-3799.md) (trickest)

## Affected products and versions

- [Spring](https://intel.threadlinqs.com/vendors/spring): Cloud Config

Affected software packages:

- `maven:org.springframework.cloud:spring-cloud-config-server` — patched in 1.4.6
- `maven:org.springframework.cloud:spring-cloud-config-server` — patched in 2.0.4
- `maven:org.springframework.cloud:spring-cloud-config-server` — patched in 2.1.2

## How to fix CVE-2019-3799

The record marks a vendor fix as available for CVE-2019-3799. Fixed versions are recorded for 3 packages: maven:org.springframework.cloud:spring-cloud-config-server 1.4.6, maven:org.springframework.cloud:spring-cloud-config-server 2.0.4, maven:org.springframework.cloud:spring-cloud-config-server 2.1.2. Patch reference: [https://www.oracle.com/security-alerts/cpuapr2022.html](https://www.oracle.com/security-alerts/cpuapr2022.html). Vendor advisory: [https://pivotal.io/security/cve-2019-3799](https://pivotal.io/security/cve-2019-3799). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2019-3799

No threat campaign in the Threadlinqs corpus currently references CVE-2019-3799, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories, ProjectDiscovery Nuclei. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [pivotal.io](https://pivotal.io/security/cve-2019-3799)

**Other references**

- [oracle.com](https://www.oracle.com/security-alerts/cpuapr2022.html)

Canonical: https://intel.threadlinqs.com/cve/CVE-2019-3799
No Threadlinqs detection currently covers CVE-2019-3799; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
