Skip to content

Spring Boot EndpointRequest.to() creates wrong matcher if actuator endpoint is not exposed

High severity GitHub Reviewed Published Apr 28, 2025 to the GitHub Advisory Database • Updated Apr 28, 2025

Package

maven org.springframework.boot:spring-boot (Maven)

Affected versions

<= 2.7.24.2
>= 3.1.0, <= 3.1.15.2
>= 3.2.0, <= 3.2.13.2
>= 3.3.0, <= 3.3.10
>= 3.4.0, <= 3.4.4

Patched versions

3.3.11
3.4.5

Description

EndpointRequest.to() creates a matcher for null/** if the actuator endpoint, for which the EndpointRequest has been created, is disabled or not exposed.

Your application may be affected by this if all the following conditions are met:

  • You use Spring Security
  • EndpointRequest.to() has been used in a Spring Security chain configuration
  • The endpoint which EndpointRequest references is disabled or not exposed via web
  • Your application handles requests to /null and this path needs protection

You are not affected if any of the following is true:

  • You don't use Spring Security
  • You don't use EndpointRequest.to()
  • The endpoint which EndpointRequest.to() refers to is enabled and is exposed
  • Your application does not handle requests to /null or this path does not need protection

References

Published by the National Vulnerability Database Apr 28, 2025
Published to the GitHub Advisory Database Apr 28, 2025
Reviewed Apr 28, 2025
Last updated Apr 28, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(21st percentile)

Weaknesses

CVE ID

CVE-2025-22235

GHSA ID

GHSA-rc42-6c7j-7h5r

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.