Skip to main content
HighInfo disclosureOWASP A05:2021CWE-200

How to fix: Spring Boot Actuator endpoint publicly accessible

A Spring Boot Actuator endpoint (/actuator, /health, /env, /metrics, etc.) is publicly accessible.

Why it matters

Exposed Actuator endpoints can reveal environment variables (including secrets), heap dumps, thread dumps, application configuration, database connection strings, and enable remote shutdown, depending on which endpoints are exposed.

Spring Boot Actuator provides operational endpoints for monitoring. In production, these must be restricted to internal networks or secured with authentication.

How to fix it

  1. 1Expose only the health endpoint publicly: management.endpoints.web.exposure.include=health
  2. 2Move management server to a separate internal port: management.server.port=8081
  3. 3Require authentication for all actuator endpoints
  4. 4Disable /env, /heapdump, /threaddump, and /shutdown entirely in production

Code examples

application.yml: restrict actuator

YAML
management:
  endpoints:
    web:
      exposure:
        include: "health"
  endpoint:
    health:
      show-details: never
  server:
    port: 8081  # internal port only

References

Detected automatically by VulnRadar. The check id is spring-boot-actuator-exposed, stable across every scan so you can filter or diff on it.

See every info disclosure check

Questions

How severe is Spring Boot Actuator endpoint publicly accessible?
VulnRadar rates this high severity in the info disclosure 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-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Spring Boot Actuator endpoint publicly accessible 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.

Propose a checkHow a check is built

Scan your own site for spring boot actuator endpoint publicly accessible

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

Spring Boot Actuator endpoint publicly accessible | VulnRadar