Skip to content
Fencer Vulns
critical 9.8

CVE-2023-20873 in the critical feed json

Spring Boot Security Bypass with Wildcard Pattern Matching on Cloud Foundry

published 2023-04-20 3 y ago modified 2026-06-17 4 mo ago also GHSA-g5h3-w546-pj7f , EUVD-2023-1303

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits
0
none known

Summary

In Spring Boot versions 3.0.0 - 3.0.5, 2.7.0 - 2.7.10, and older unsupported versions, an application that is deployed to Cloud Foundry could be susceptible to a security bypass. Users of affected versions should apply the following mitigation: 3.0.x users should upgrade to 3.0.6+. 2.7.x users should upgrade to 2.7.11+. Users of older, unsupported versions should upgrade to 3.0.6+ or 2.7.11+.

Patch / fix

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-20873 updated cvss 9.8

spring-boot: Security Bypass With Wildcard Pattern Matching on Cloud Foundry

  • Red Hat Decision Manager 7 spring-boot
    affected: workaround, no fix available “Disable Cloud Foundry actuator endpoints by setting 'management.cloudfoundry.enabled' to false.”
  • Red Hat JBoss Fuse Service Works 6 spring-boot
    affected: workaround, no fix planned “Disable Cloud Foundry actuator endpoints by setting 'management.cloudfoundry.enabled' to false.”
  • Red Hat Process Automation 7 spring-boot Red Hat Single Sign-On 7 spring-boot Red Hat support for Spring Boot spring-boot
    affected: workaround, no fix available “Disable Cloud Foundry actuator endpoints by setting 'management.cloudfoundry.enabled' to false.”
  • Red Hat AMQ Streams 2.6.0
    fixed: vendor fix “Disable Cloud Foundry actuator endpoints by setting 'management.cloudfoundry.enabled' to false.” RHSA-2023:7678
  • Red Hat RHINT Camel-Springboot 3.18.3.2
    fixed: vendor fix “Disable Cloud Foundry actuator endpoints by setting 'management.cloudfoundry.enabled' to false.” RHSA-2023:5147
  • Red Hat RHINT Camel-Springboot 3.20.2
    fixed: vendor fix “Disable Cloud Foundry actuator endpoints by setting 'management.cloudfoundry.enabled' to false.” RHSA-2023:5148
  • Red Hat A-MQ Clients 2 spring-boot Red Hat Migration Toolkit for Runtimes spring-boot Red Hat AMQ Broker 7 spring-boot Red Hat build of OptaPlanner 8 spring-boot Red Hat Data Grid 8 spring-boot Red Hat Enterprise Linux 8 log4j, log4j-jcl, log4j-web, log4j-slf4j
    +10 more products
    Red Hat Enterprise Linux 9 log4j, log4j-jcl, log4j-slf4j Red Hat Fuse 7 spring-boot Red Hat Integration Camel K 1 spring-boot Red Hat JBoss Data Grid 7 spring-boot Red Hat JBoss Enterprise Application Platform 6 spring-boot Red Hat JBoss Enterprise Application Platform 7 spring-boot Red Hat JBoss Enterprise Application Platform 8 spring-boot Red Hat JBoss Enterprise Application Platform Expansion Pack spring-boot Red Hat JBoss Fuse 6 spring-boot Red Hat OpenShift Application Runtimes spring-boot
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
18 mo ago

Exploit prediction

1.12% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.springframework.boot:spring-boot-actuator-autoconfigure
>=3.0.0, <3.0.6
>=2.7.0, <2.7.11
>=2.6.0, <2.6.15
<2.5.15
3.0.6
2.7.11
2.6.15
2.5.15

Affected products

  • n/a Spring Boot

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.