LiveActive security incident?Get immediate response
CVE Record

CVE-2025-34171: CasaOS <= 0.4.15 Unauthenticated File and Debug Data Exposure

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.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CasaOS up to and including 0.4.15 exposes unauthenticated web endpoints that can reveal configuration and system debug information. A reachable instance could disclose installed application details, host OS, kernel, hardware, storage information, and file-existence signals. The provided sources describe reconnaissance value, not direct code execution.

Executive priority

Treat this as a moderate-priority exposure reduction issue. It may not be an immediate breach indicator, but unauthenticated disclosure from infrastructure management software can materially improve an attacker’s targeting and should be removed from public reach quickly.

Technical view

The advisory describes missing authentication and information exposure in CasaOS endpoints. One endpoint accepts a user-controlled path and can read files under /var/lib/casaos/1/. Another discloses system debug data. Distinct error messages may allow file-existence enumeration. Mapped weaknesses are CWE-497 and CWE-862.

Likely exposure

Likely exposure is CasaOS deployments running versions up to and including 0.4.15 where the affected web/API endpoints are reachable by untrusted users. The source bundle does not provide CPEs, deployment defaults, or a confirmed fixed version.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. CVSS 4.0 rates the issue 6.9 with network access, low complexity, no privileges, and no user interaction, making opportunistic reconnaissance plausible on exposed systems.

Researcher notes

Evidence is limited to the provided CVE and VulnCheck-style advisory data. Do not infer remote code execution, credential theft, active exploitation, or a patched version from this bundle. Key research tasks are version validation, exposure mapping, and log review.

Mitigation direction

  • Check IceWhale/CasaOS vendor guidance for a fixed release or official workaround.
  • Upgrade CasaOS when a vendor-supported fixed version is confirmed.
  • Restrict CasaOS access to trusted networks or VPN-only administration paths.
  • Block unauthenticated internet access to CasaOS management endpoints.
  • Review exposed hosts for leaked configuration or reconnaissance indicators.

Validation and detection

  • Inventory CasaOS versions and identify any systems at or below 0.4.15.
  • Confirm whether CasaOS web/API endpoints are reachable from untrusted networks.
  • Review access logs for unauthenticated requests to the affected endpoint paths.
  • Validate remediation by confirming restricted access or vendor-confirmed updated versions.
  • Check configuration exposure assumptions against vendor documentation before closure.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-497: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-34171 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NVulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2025-34171Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IceWhale TechCasaOS0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-497 · source CWE mapping

Exposure of Sensitive System Information to an Unauthorized Control Sphere

Exposure of Sensitive System Information to an Unauthorized Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.