Spring Cloud Gateway vulnerabilitiesAnd the versions its exploited flaws hit.
Spring Cloud Gateway is made by VMware. We track 3 published vulnerabilities in it, across 41 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 16 May 2022. If you run Spring Cloud Gateway, check your version against the exploited flaws below and patch those first.
The most recent Spring Cloud Gateway flaw added to the known-exploited list is CVE-2022-22947, on 16 May 2022. We keep watching the known-exploited list.
Which versions of Spring Cloud Gateway do the exploited flaws hit?
Each exploited flaw lists the versions it affects, usually as ranges. "before 3.0.7" means every version up to, but not including, 3.0.7. Find your version, then patch.
- CVE-2022-22947Exploited list, 16 May 2022
VMware Spring Cloud Gateway Code Injection Vulnerability
before 3.0.73.1.0
Which Spring Cloud Gateway 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.
- 10.0VMware Spring Cloud Gateway Code Injection Vulnerability
Spring Cloud Gateway applications are vulnerable to a code injection attack when the Gateway Actuator endpoint is enabled, exposed and unsecured.
Which Spring Cloud Gateway 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.
- 98%
In spring cloud gateway versions prior to 3.1.1+ and 3.0.7+ , applications are vulnerable to a code injection attack when the Gateway Actuator endpoint is enabled, exposed and unsecured.
- 4.8%CVE-2022-22946Medium
In spring cloud gateway versions prior to 3.1.1+ , applications that are configured to enable HTTP2 and no key store or trusted certificates are set will be configured to use an insecure TrustManager.
- 0.7%CVE-2021-22051Medium
Applications using Spring Cloud Gateway are vulnerable to specifically crafted requests that could make an extra request on downstream services.
Running Spring Cloud Gateway? 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 Cloud Gateway applications are vulnerable to a code injection attack when the Gateway Actuator endpoint is enabled, exposed and unsecured.
- Matched to
- Spring Cloud Gateway 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 3 published vulnerabilities listed under the name Spring Cloud Gateway, across 41 versions. The most recent Spring Cloud Gateway flaw added to the known-exploited list is CVE-2022-22947, on 16 May 2022.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2022-22947.
Each flaw names its own versions, usually as ranges. The newest, CVE-2022-22947, affects before 3.0.7, 3.1.0. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Spring Cloud Gateway. 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.