# CVE-2024-24765: CasaOS-UserService allows unauthorized access to any file

> An attacker can exploit path traversal in CasaOS-UserService to read arbitrary system files, potentially leading to 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:** Yes
- **Published:** 6 Mar 2024
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h5gf-cmm8-cg7c, GO-2024-2616

## What is CVE-2024-24765?

CVE-2024-24765 is a high-severity path traversal vulnerability in IceWhaleTech CasaOS-UserService, published on 6 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CasaOS-UserService provides user management functionalities to CasaOS. Prior to version 0.4.7, path filtering of the URL for user avatar image files was not strict, making it possible to get any file on the system. This could allow an unauthorized actor to access, for example, the CasaOS user database, and possibly obtain system root privileges. Version 0.4.7 fixes this issue.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

3 open source packages ship an affected version, including github.com/IceWhaleTech/CasaOS-UserService. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/IceWhaleTech/CasaOS-UserService` | Go | All versions | 0.4.7 |
| `github.com/IceWhaleTech/CasaOS-UserService` | Go | All versions | 0.4.7 |
| `github.com/IceWhaleTech/CasaOS-UserService` | Go | All versions | 0.4.7 |

Products: Icewhale Casaos.

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

Upgrade github.com/IceWhaleTech/CasaOS-UserService to 0.4.7 or later.

## Is CVE-2024-24765 being exploited?

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

## Other vulnerabilities in IceWhaleTech CasaOS-UserService

- [CVE-2023-37265](https://insights.sbomify.com/CVE-2023-37265/): Incorrect identification of source IP addresses in CasaOS (critical 9.8)
- [CVE-2023-37266](https://insights.sbomify.com/CVE-2023-37266/): Weak json web token (JWT) secrets in CasaOS (critical 9.8)
- [CVE-2022-24193](https://insights.sbomify.com/CVE-2022-24193/): Command Injection in CasaOS (critical 9.8)
- [CVE-2024-24767](https://insights.sbomify.com/CVE-2024-24767/): CasaOS Improper Restriction of Excessive Authentication Attempts vulnerability (critical 9.1)
- [CVE-2023-37469](https://insights.sbomify.com/CVE-2023-37469/): CasaOS Command Injection vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-24765 is a high-severity path traversal vulnerability in IceWhaleTech CasaOS-UserService, published on 6 Mar 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-24765 exists.

Affected packages and fixed versions:
- github.com/IceWhaleTech/CasaOS-UserService (Go): affected all versions; fixed in 0.4.7
- github.com/IceWhaleTech/CasaOS-UserService (Go): affected all versions; fixed in 0.4.7
- github.com/IceWhaleTech/CasaOS-UserService (Go): affected all versions; fixed in 0.4.7

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-24765/ (Markdown: https://insights.sbomify.com/CVE-2024-24765/index.md)
```

## Sources

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

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