VMware Spring Cloud Gateway 3.1.0
Approved changes feed: RSS · Atom
cpe:2.3:a:vmware:spring_cloud_gateway:3.1.0:*:*:*:*:*:*:*
part: a version: 3.1.0 update: *
| Vendor | Vmware (7bb62c7c-2241-5a0b-8dbc-5f13251fb24e) |
|---|---|
| Product | Spring Cloud Gateway (8e4aae70-b458-567a-8d33-81255bb79941) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/spring-cloud/spring-cloud-gateway |
purl2cpe | 2026-06-01 10:12:21.868941 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-22947 |
vulnerable | 2026-06-08 05:40:55.611410 |
Details available
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. A remote attacker could make a maliciously crafted request that could allow arbitrary remote execution on the remote host.
Published: 2022-03-03T00:00:00.000Z
Updated: 2025-10-21T23:15:45.220Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-22946 |
vulnerable | 2026-06-08 05:40:55.605249 |
Details available
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. This makes the gateway able to connect to remote services with invalid or custom certificates.
Published: 2022-03-04T15:50:06.000Z
Updated: 2024-08-03T03:28:42.597Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.