dbcve.org
CasaosOperating system · Icewhale

CVE-2025-34171

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-02
Fix available
A fix is available. Upgrade to after 0.4.15 or later.
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
CasaOS versions up to and including 0.4.15 expose multiple unauthenticated endpoints that allow remote attackers to retrieve sensitive configuration files and system debug information. The /v1/users/image endpoint can be abused with a user-controlled path parameter to access files under /var/lib/casaos/1/, which reveals installed applications and configuration details. Additionally, /v1/sys/debug discloses host operating system, kernel, hardware, and storage information. The endpoints also return distinct error messages, enabling file existence enumeration of arbitrary paths on the underlying host filesystem. This information disclosure can be used for reconnaissance and to facilitate targeted follow-up attacks against services deployed on the host.

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

CasaOS versions up to 0.4.15 contain unauthenticated path traversal via the /v1/users/image endpoint allowing attackers to read arbitrary files under /var/lib/casaos/1/, exposing app configurations and sensitive data. The /v1/sys/debug endpoint separately leaks host OS, kernel, hardware, and storage details. Both endpoints return distinct error messages enabling file existence enumeration across the host filesystem.

MitigationRestrict access to /v1/users/image and /v1/sys/debug endpoints by implementing authentication, apply strict path validation to prevent traversal, and suppress detailed error messages to block enumeration.

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
CasaosOperating system
Affected:<= 0.4.15

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 CasaOS version
    Check the installed CasaOS version on the system. On Linux systems, this may be found via 'casaos --version', checking the package manager, or reviewing the docker container version if running as a container.
    Affected if Installed version is 0.4.15 or lower
  2. Verify /v1/users/image endpoint accessibility
    Send a GET request to http://localhost:port/v1/users/image (replace port with the CasaOS web interface port, commonly 3000 or 8080) without any authentication headers.
    Affected if The endpoint returns any response without requiring authentication
  3. Test path traversal on /v1/users/image
    Send a GET request to http://localhost:port/v1/users/image with a path traversal payload such as ../../../../etc/passwd or a file within /var/lib/casaos/1/ directory.
    Affected if The endpoint returns file contents or different error messages that indicate the file exists versus does not exist
  4. Verify /v1/sys/debug endpoint accessibility
    Send a GET request to http://localhost:port/v1/sys/debug without authentication.
    Affected if The endpoint returns OS, kernel, hardware, or storage information without requiring authentication

A system is affected if it runs CasaOS version 0.4.15 or lower and exposes either the /v1/users/image or /v1/sys/debug endpoints 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.

From vendor data
Upgrade available Upgrade to a release after 0.4.15
Interim mitigation

Restrict access to /v1/users/image and /v1/sys/debug endpoints by implementing authentication, apply strict path validation to prevent traversal, and suppress detailed error messages to block enumeration.

Fix this in Casaos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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