Spring Cloud Config vulnerabilitiesAnd the versions its exploited flaws hit.
Spring Cloud Config is made by VMware. We track 4 published vulnerabilities in it, across 45 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 25 March 2022. If you run Spring Cloud Config, check your version against the exploited flaws below and patch those first.
The most recent Spring Cloud Config flaw added to the known-exploited list is CVE-2020-5410, on 25 March 2022. We keep watching the known-exploited list.
Which versions of Spring Cloud Config do the exploited flaws hit?
Each exploited flaw lists the versions it affects, usually as ranges. "2.1.0 to before 2.1.9" means from 2.1.0 up to, but not including, 2.1.9. Find your version, then patch.
- CVE-2020-5410Exploited list, 25 Mar 2022
VMware Tanzu Spring Cloud Config Directory Traversal Vulnerability
2.1.0 to before 2.1.92.2.0 to before 2.2.3
Which Spring Cloud Config vulnerabilities are being exploited?
1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 7.5VMware Tanzu Spring Cloud Config Directory Traversal Vulnerability
Spring, by VMware Tanzu, Cloud Config contains a path traversal vulnerability that allows applications to serve arbitrary configuration files.
Which Spring Cloud Config flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 96%
Spring Cloud Config, versions 2.2.x prior to 2.2.3, versions 2.1.x prior to 2.1.9, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module.
- 85%CVE-2019-3799Medium
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...
- 69%CVE-2020-5405Medium
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.
- 0.2%CVE-2023-20859Medium
In Spring Vault, versions 3.0.x prior to 3.0.2 and versions 2.3.x prior to 2.3.3 and older versions, an application is vulnerable to insertion of sensitive information into a log file when it attempts to revoke a...
Running Spring Cloud Config? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
Spring, by VMware Tanzu, Cloud Config contains a path traversal vulnerability that allows applications to serve arbitrary configuration files.
- Matched to
- Spring Cloud Config on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 4 published vulnerabilities listed under the name Spring Cloud Config, across 45 versions. The most recent Spring Cloud Config flaw added to the known-exploited list is CVE-2020-5410, on 25 March 2022.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2020-5410.
Each flaw names its own versions, usually as ranges. The newest, CVE-2020-5410, affects 2.1.0 to before 2.1.9, 2.2.0 to before 2.2.3. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Spring Cloud Config. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.