How to fix: Spring Boot Actuator Endpoints Exposed
Spring Boot Actuator endpoints found in page source.
Why it matters
Actuator endpoints expose env vars, beans, mappings, and health status.
Spring Boot Actuator provides operational endpoints that should be secured.
How to fix it
- 1Restrict actuator endpoints to internal access only.
- 2Use Spring Security to protect actuator.
Code examples
Restrict Spring Boot Actuator endpoints
# application.yml: expose only health endpoint publicly
management:
endpoints:
web:
exposure:
include: "health"
endpoint:
health:
show-details: never
server:
port: 8081 # separate internal port, not exposed to internetReferences
Detected automatically by VulnRadar. The check id is spring-boot-actuator, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is Spring Boot Actuator Endpoints Exposed?
- VulnRadar rates this high severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id spring-boot-actuator, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Spring Boot Actuator Endpoints Exposed map to?
- It maps to CWE-200. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.