What is the severity of CVE-2020-5405?

CVE-2020-5405 is classified as a High severity vulnerability due to the potential for unauthorized access to sensitive configuration files.

How do I fix CVE-2020-5405?

To fix CVE-2020-5405, upgrade to Spring Cloud Config versions 2.2.2 or 2.1.7 or later.

What systems are affected by CVE-2020-5405?

CVE-2020-5405 affects VMware Tanzu Spring Cloud Config versions prior to 2.2.2 and 2.1.7.

What kind of attacks can exploit CVE-2020-5405?

An attacker can exploit CVE-2020-5405 to serve arbitrary configuration files, potentially leading to data leaks.

Is there a patch available for CVE-2020-5405?

Yes, a patch is available in the specified versions of Spring Cloud Config, which resolves the vulnerability.

Vulnerability/
CVE-2020-5405

medium

6.5

CWE

22 23

5/3/2020

16/9/2024

CVE-2020-5405: Directory Traversal with spring-cloud-config-server

First published: Thu Mar 05 2020(Updated: )

Spring Cloud Config, versions 2.2.x prior to 2.2.2, versions 2.1.x prior to 2.1.7, 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.

Credit: security@pivotal.io

Affected Software	Affected Version	How to fix
VMware Tanzu Spring Cloud Configuration Server	>=2.1.0<2.1.7
VMware Tanzu Spring Cloud Configuration Server	>=2.2.0<2.2.2

Never miss a vulnerability like this again

Reference Links

https://pivotal.io/security/cve-2020-5405

Frequently Asked Questions

What is the severity of CVE-2020-5405?
CVE-2020-5405 is classified as a High severity vulnerability due to the potential for unauthorized access to sensitive configuration files.
How do I fix CVE-2020-5405?
To fix CVE-2020-5405, upgrade to Spring Cloud Config versions 2.2.2 or 2.1.7 or later.
What systems are affected by CVE-2020-5405?
CVE-2020-5405 affects VMware Tanzu Spring Cloud Config versions prior to 2.2.2 and 2.1.7.
What kind of attacks can exploit CVE-2020-5405?
An attacker can exploit CVE-2020-5405 to serve arbitrary configuration files, potentially leading to data leaks.
Is there a patch available for CVE-2020-5405?
Yes, a patch is available in the specified versions of Spring Cloud Config, which resolves the vulnerability.

agent/type
agent/author
agent/severity
agent/references
agent/title
agent/weakness
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/softwarecombine
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/vmware
canonical/vmware tanzu spring cloud configuration server
version/vmware tanzu spring cloud configuration server/2.1.0
version/vmware tanzu spring cloud configuration server/2.2.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2020-5405?
CVE-2020-5405 is classified as a High severity vulnerability due to the potential for unauthorized access to sensitive configuration files.
How do I fix CVE-2020-5405?
To fix CVE-2020-5405, upgrade to Spring Cloud Config versions 2.2.2 or 2.1.7 or later.
What systems are affected by CVE-2020-5405?
CVE-2020-5405 affects VMware Tanzu Spring Cloud Config versions prior to 2.2.2 and 2.1.7.
What kind of attacks can exploit CVE-2020-5405?
An attacker can exploit CVE-2020-5405 to serve arbitrary configuration files, potentially leading to data leaks.
Is there a patch available for CVE-2020-5405?
Yes, a patch is available in the specified versions of Spring Cloud Config, which resolves the vulnerability.