dbcve.org
Spring Boot Actuator LogviewFramework / library · Spring Boot Actuator Logview Project

CVE-2023-29986

MEDIUM · 5.3 CVSS v3.1 Published 2023-05-11
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
spring-boot-actuator-logview 0.2.13 allows Directory Traversal to sibling directories via LogViewEndpoint.view.

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 · high confidence

The spring-boot-actuator-logview library version 0.2.13 contains a path traversal vulnerability in the LogViewEndpoint.view endpoint. By using directory traversal sequences (e.g., '../'), an unauthenticated attacker can escape the intended log directory and access files in sibling directories on the host filesystem, potentially exposing sensitive configuration or data files accessible to the application process.

MitigationUpgrade to a patched version of spring-boot-actuator-logview if available; otherwise, disable the logview actuator endpoint in production or implement strict path validation that normalizes and validates the requested path before file access.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring Boot Actuator LogviewFramework / library
Affected:= 0.2.13

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 spring-boot-actuator-logview in dependencies
    Inspect your project's dependency manifest (pom.xml, build.gradle, requirements.txt, or similar). Search for 'spring-boot-actuator-logview' or 'logview' in the dependency list.
    Affected if The library is present and its version is 0.2.13.
  2. Verify the exact library version
    Check the resolved library version in your build output, Maven/Gradle dependency tree, or the JAR file's manifest within your deployed application. Confirm the version equals 0.2.13.
    Affected if The installed version is exactly 0.2.13.
  3. Confirm logview actuator endpoint is enabled
    Inspect your application.properties or application.yml for 'management.endpoints.web.exposure.include' or similar actuator configuration. Look for 'logview' in the exposed endpoints list.
    Affected if The logview endpoint is included in the exposed actuator endpoints.
  4. Check if endpoint is accessible without authentication
    Review your Spring Security configuration (SecurityFilterChain, WebSecurityConfigurerAdapter, or annotation-based security) to determine if the '/actuator/logview' path permits unauthenticated access.
    Affected if The logview endpoint is accessible without authentication (no security constraint or permitAll).

You are affected if spring-boot-actuator-logview version 0.2.13 is in use AND the logview actuator endpoint is exposed and accessible without authentication.

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

Upgrade to a patched version of spring-boot-actuator-logview if available; otherwise, disable the logview actuator endpoint in production or implement strict path validation that normalizes and validates the requested path before file access.

Recommended fix Moderate confidence

Fixed release (check upstream repository for post-0.2.13 versions that address CWE-22)

  1. 1. Verify current vulnerable version by checking project dependencies (e.g., mvn dependency:tree or build.gradle) for spring-boot-actuator-logview version 0.2.13
  2. 2. Identify an alternative or newer version of spring-boot-actuator-logview that addresses the path traversal vulnerability
  3. 3. If a newer fixed version is available from the maintainer, update the dependency version in your build configuration (pom.xml, build.gradle, etc.)
  4. 4. Rebuild and redeploy the application
  5. 5. Verify the fix by testing that directory traversal attempts via the /logview endpoint are now blocked
  6. 6. Consider disabling the logview actuator endpoint entirely if not needed in production environments as an additional defense-in-depth measure

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

Fix this in Spring Boot Actuator Logview Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-29986 — 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-2023-29986 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