Spring Boot Actuator Endpoints Exposed
Spring Boot Actuator management endpoints are reachable without authentication, exposing configuration, memory contents and administrative functions.
| Severity | High |
| CVSS 3.1 | 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Open in the calculator |
| CVSS 4.0 | 8.7 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-306: Missing Authentication for Critical Function |
| OWASP Top 10 | A07:2025 Authentication Failures |
| MITRE ATT&CK | T1552 Unsecured Credentials, T1539 Steal Web Session Cookie |
| Category | Information Disclosure |
Description
Spring Boot Actuator adds management endpoints to an application, usually under /actuator or, in old versions, at the root (for example /env and /heapdump), and these endpoints are reachable over HTTP without authentication. Endpoints commonly found exposed include env and configprops (configuration properties and their sources), heapdump (a full dump of the Java heap), threaddump, mappings (every route in the application), beans, loggers (which accepts changes to log levels), httpexchanges or the older httptrace and trace (recent requests with their headers) and, where enabled, shutdown, as well as endpoints added by other libraries, such as gateway and jolokia.
Current versions expose only the health endpoint over HTTP by default and mask the values shown by env and configprops, so exposure usually comes from configuration such as management.endpoints.web.exposure.include=* without matching security rules, or from older versions. The masking does not apply to the heap dump, which holds the real values of everything in memory: typically database and service credentials, API keys, encryption keys, the session identifiers of signed-in users and fragments of recent requests, which can lead to account takeover and access to connected systems.
Other endpoints disclose the application's full route map and configuration, allow log levels to be changed or, where enabled, the application to be shut down, and in some versions and configurations endpoints such as gateway and jolokia have allowed code execution. What an attacker obtains therefore depends on which endpoints are exposed, and the impact is high whenever heapdump or an unmasked env is among them.
The weakness is identified by requesting /actuator, which lists the exposed endpoints, and the individual endpoint paths, including under alternative base paths and on a separate management port. A downloaded heap dump can be searched with Java heap analysis tools.
Remediation
Expose only the endpoints that are needed, and require authentication for every other one:
- Limit web exposure to what monitoring needs, usually
health, withmanagement.endpoints.web.exposure.include=health, and never use*in production. - Protect any further endpoints with Spring Security, requiring an administrative role for actuator requests, as below.
- Serve management endpoints on a separate port bound to a loopback or internal address, with
management.server.portandmanagement.server.address, and block/actuatorat the reverse proxy or load balancer. - Disable endpoints that are not needed, particularly
heapdump,env,shutdownandjolokia, and keep the masking of values inenvandconfigprops. - If
heapdumpor an unmaskedenvwas exposed, rotate every secret the application holds and invalidate active sessions.
Confirm the fix by requesting /actuator and each previously exposed endpoint from an untrusted network: each should be refused or not found.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.