dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-8738

MEDIUM · 5.3 CVSS v3.1 Published 2025-08-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been found in zlt2000 microservices-platform up to 6.0.0 and classified as problematic. This vulnerability affects unknown code of the file /actuator of the component Spring Actuator Interface. The manipulation leads to information disclosure. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The zlt2000 microservices-platform exposes Spring Actuator endpoints (/actuator) without proper access controls, allowing remote attackers to retrieve sensitive configuration data, environment variables, health metrics, or internal application details. The public exploit availability indicates the attack is straightforward and requires no authentication.

MitigationRestrict access to Spring Actuator endpoints via Spring Security, network segmentation, or disable unused actuator endpoints in production. Conduct a full audit of all exposed endpoints and the sensitivity of data they reveal.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the application is zlt2000 microservices-platform
    Review application documentation, source code repositories, or deployment artifacts for references to 'zlt2000' or 'microservices-platform'. Check the application's pom.xml, package.json, or similar dependency manifests for the zlt2000 framework.
    Affected if The application uses the zlt2000 microservices-platform framework.
  2. Verify if Spring Actuator endpoints are exposed
    Attempt to access the /actuator endpoint or common actuator paths such as /actuator/health, /actuator/env, /actuator/info, /actuator/beans, /actuator/mappings by making an HTTP GET request to these URLs from an unauthenticated context.
    Affected if The /actuator base path or any actuator sub-endpoints return HTTP 200 OK instead of 401/403 authentication errors.
  3. Check if actuator endpoints require authentication
    Send HTTP requests to actuator endpoints without providing any authentication headers or credentials. Inspect the HTTP response status code and any authentication challenges returned.
    Affected if Sensitive actuator endpoints such as /actuator/env, /actuator/beans, /actuator/configprops, or /actuator/mappings return application data without requiring authentication.
  4. Inspect the Spring Security configuration
    Review the application's Spring Security configuration files (typically in Java config classes annotated with @EnableWebSecurity or XML configuration) to verify if the actuator paths are explicitly secured or excluded from security constraints.
    Affected if The Spring Security configuration does not restrict access to /actuator/** paths, or these paths are explicitly permitted without authentication.
  5. Review application configuration for actuator exposure
    Check application.properties or application.yml for 'management.endpoints.web.exposure.include' settings. Verify if sensitive endpoints like 'env', 'beans', 'configprops', 'heapdump', or 'threaddump' are listed in the exposed endpoints.
    Affected if The management.endpoints.web.exposure.include property includes sensitive endpoints without corresponding access restrictions, or no security configuration exists for actuator endpoints.

A user is affected if they are running the zlt2000 microservices-platform with Spring Actuator endpoints accessible without authentication, allowing unauthenticated access to sensitive configuration and environment data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access to Spring Actuator endpoints via Spring Security, network segmentation, or disable unused actuator endpoints in production. Conduct a full audit of all exposed endpoints and the sensitivity of data they reveal.

Recommended fix Low confidence
  1. Add or update application.properties to disable sensitive Spring Actuator endpoints: management.endpoints.web.exposure.include="health,info" and management.endpoints.enabled-by-default=false
  2. Alternatively, disable specific sensitive endpoints: management.endpoint.env.enabled=false, management.endpoint.configprops.enabled=false, management.endpointheapdump.enabled=false, management.endpointthreaddump.enabled=false
  3. If Spring Security is used, add security configuration to restrict access to /actuator endpoints: antMatchers("/actuator/**").hasRole("ADMIN") or fully disable actuator in security config
  4. For production environments, consider using a separate management port: management.server.port=8081 to isolate management endpoints from main application traffic
  5. Restart the application after applying configuration changes
  6. Verify that sensitive information is no longer exposed by accessing the /actuator endpoint directly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8738 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8738 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data