How severe is GHSA-h5gf-cmm8-cg7c?

GHSA-h5gf-cmm8-cg7c has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-h5gf-cmm8-cg7c?

GHSA-h5gf-cmm8-cg7c affects the following packages: github.com/IceWhaleTech/CasaOS-UserService (Go). Ecosystems affected: Go.

How do I fix GHSA-h5gf-cmm8-cg7c?

Update github.com/IceWhaleTech/CasaOS-UserService to 0.4.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h5gf-cmm8-cg7c is resolved across your whole dependency graph.

How do I detect GHSA-h5gf-cmm8-cg7c in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/IceWhaleTech/CasaOS-UserService. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-h5gf-cmm8-cg7c if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-h5gf-cmm8-cg7c?

O3 pinpoints whether GHSA-h5gf-cmm8-cg7c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-h5gf-cmm8-cg7c actively exploited in the wild?

No public exploit code has been indexed for GHSA-h5gf-cmm8-cg7c yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-h5gf-cmm8-cg7c?

GHSA-h5gf-cmm8-cg7c has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 57th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-h5gf-cmm8-cg7c?

GHSA-h5gf-cmm8-cg7c is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-h5gf-cmm8-cg7c published, and has it been updated?

GHSA-h5gf-cmm8-cg7c was published on March 6, 2024 and was last updated on March 12, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-h5gf-cmm8-cg7c: CasaOS-UserService allows unauthorized acc…

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk57th percentile+0.51%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐹github.com/IceWhaleTech/CasaOS-UserService

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

http://demo.casaos.io/v1/users/image?path=/var/lib/casaos/1/avatar.png

Originally it was to get the url of the user's avatar, but the path filtering was not strict, making it possible to get any file on the system.

Details

Construct paths to get any file.

Such as the CasaOS user database, and furthermore can obtain system root privileges.

PoC

http://demo.casaos.io/v1/users/image?path=/var/lib/casaos/conf/../db/user.db

Impact

v0.4.6 all previous versions

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/IceWhaleTech/CasaOS-UserService`	all versions	0.4.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/IceWhaleTech/CasaOS-UserService. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/IceWhaleTech/CasaOS-UserService to 0.4.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h5gf-cmm8-cg7c is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-h5gf-cmm8-cg7c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-h5gf-cmm8-cg7c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary http://demo.casaos.io/v1/users/image?path=/var/lib/casaos/1/avatar.png Originally it was to get the url of the user's avatar, but the path filtering was not strict, making it possible to get any file on the system. ### Details Construct paths to get any file. Such as the CasaOS user database, and furthermore can obtain system root privileges. ### PoC http://demo.casaos.io/v1/users/image?path=/var/lib/casaos/conf/../db/user.db ### Impact v0.4.6 all previous versions

O3 Security · Impact-Aware SCA

Is GHSA-h5gf-cmm8-cg7c in your dependencies?

O3 detects GHSA-h5gf-cmm8-cg7c across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-h5gf-cmm8-cg7c