# CVE-2024-48931: ZimaOS Arbitrary File Read via Parameter Manipulation

> Authenticated attackers can read sensitive system files like /etc/shadow via path traversal in the ZimaOS API, enabling potential privilege escalation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Oct 2024
- **Updated:** 25 Oct 2024
- **Also known as:** GHSA-hjw2-9gq5-qgwj

## What is CVE-2024-48931?

CVE-2024-48931 is a high-severity path traversal vulnerability in IceWhaleTech ZimaOS, published on 24 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ZimaOS is a fork of CasaOS, an operating system for Zima devices and x86-64 systems with UEFI. In version 1.2.4 and all prior versions, the ZimaOS API endpoint `http://<Zima_Server_IP:PORT>/v3/file?token=<token>&files=<file_path>` is vulnerable to arbitrary file reading due to improper input validation. By manipulating the `files` parameter, authenticated users can read sensitive system files, including `/etc/shadow`, which contains password hashes for all users. This vulnerability exposes critical system data and poses a high risk for privilege escalation or system compromise. The vulnerability occurs because the API endpoint does not validate or restrict file paths provided via the `files` parameter. An attacker can exploit this by manipulating the file path to access sensitive files outside the intended directory. As of time of publication, no known patched versions are available.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-48931?

It affects 1 product.


Products: Zimaspace Zimaos.

## How do I fix CVE-2024-48931?

No fix has been published for CVE-2024-48931 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-48931 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48931 exists.

## Other vulnerabilities in IceWhaleTech ZimaOS

- [CVE-2026-21891](https://insights.sbomify.com/CVE-2026-21891/): ZimaOS has Authentication Bypass via System-Level Username (critical 9.4)
- [CVE-2026-28798](https://insights.sbomify.com/CVE-2026-28798/): Arbitrary internal service access via /v1/sys/proxy when Cloudflare Tunnel is enabled on ZimaOS (critical 9.1)
- [CVE-2026-28442](https://insights.sbomify.com/CVE-2026-28442/): ZimaOS: Arbitrary Deletion of Internal System Files via API Path Manipulation (high 8.6)
- [CVE-2026-28286](https://insights.sbomify.com/CVE-2026-28286/): ZimaOS: Unauthorized Creation of Files/Folders in Restricted System Directories via API (high 8.6)
- [CVE-2024-49357](https://insights.sbomify.com/CVE-2024-49357/): ZimaOS (Installed Applications and System Information) has Unauthorized Sensitive Data Leak (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-48931 and fix it if it is affected.

What it is: CVE-2024-48931 is a high-severity path traversal vulnerability in IceWhaleTech ZimaOS, published on 24 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48931 exists.

Affected product: IceWhaleTech ZimaOS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-48931/ (Markdown: https://insights.sbomify.com/CVE-2024-48931/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-48931
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-48931
- OSV: https://osv.dev/vulnerability/CVE-2024-48931

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-48931/
Summaries are generated and may contain mistakes; the official description above is the record.