Is CVE-2020-5410 exploited in the wild?

Yes. CVE-2020-5410 is known to be exploited in the wild, first recorded on 25 March 2022. Treat it as urgent.

How severe is CVE-2020-5410?

Critical severity, with a CVSS score of 3.1, published 5 June 2020.

Which products and versions are affected?

org.springframework.cloud:spring-cloud-config-server (Maven) ECOSYSTEM:introduced=2.1.0,fixed=2.1.9.

Is there a fix for CVE-2020-5410?

Yes. org.springframework.cloud:spring-cloud-config-server (Maven): upgrade to 2.1.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2020-5410 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2020-5410?

Check whether you run org.springframework.cloud:spring-cloud-config-server (Maven), VMware Tanzu Spring Cloud Config Server or VMware Tanzu Spring Cloud Configuration (Config) Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2020-5410: Directory traversal attack in Spring Cloud Config

CVE-2020-5410 · Severity: critical · CVSS 3.1 · Exploited in the wild · Published 2020-06-05

Spring Cloud Config contains a directory traversal vulnerability in the spring-cloud-config-server module. An unauthenticated attacker can send specially crafted URLs to access and serve arbitrary configuration files from the server's file system.

Technologies: org.springframework.cloud:spring-cloud-config-server (Maven). Vendors: Maven.

Quick answers

Is CVE-2020-5410 exploited in the wild?: Yes. CVE-2020-5410 is known to be exploited in the wild, first recorded on 25 March 2022. Treat it as urgent.
How severe is CVE-2020-5410?: Critical severity, with a CVSS score of 3.1, published 5 June 2020.
Which products and versions are affected?: org.springframework.cloud:spring-cloud-config-server (Maven) ECOSYSTEM:introduced=2.1.0,fixed=2.1.9.
Is there a fix for CVE-2020-5410?: Yes. org.springframework.cloud:spring-cloud-config-server (Maven): upgrade to 2.1.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2020-5410 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2020-5410?: Check whether you run org.springframework.cloud:spring-cloud-config-server (Maven), VMware Tanzu Spring Cloud Config Server or VMware Tanzu Spring Cloud Configuration (Config) Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

org.springframework.cloud:spring-cloud-config-server (Maven): upgrade to 2.1.9 or later

# set org.springframework.cloud:spring-cloud-config-server to 2.1.9 in your pom.xml or build.gradle

Affected products

VMware Tanzu Spring Cloud Config 2.1.x prior to 2.1.9, 2.2.x prior to 2.2.3

Identifiers

CVE-2020-5410
GHSA-32xf-jwmv-9hf3

Timeline

2020-06-02: disclosed: NVD Published Date
2022-03-25: kev added: Added to CISA Known Exploited Vulnerabilities Catalog

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.