# GHSA-cvmj-47v9-35m9: FUSE-Rust: Uninitalized memory read and leak caused by fuser crate

> An attacker can read uninitialized memory and leak sensitive data due to incorrect NULL argument handling in the fuser crate.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Sep 2021
- **Also known as:** RUSTSEC-2021-0154

## What is GHSA-cvmj-47v9-35m9?

GHSA-cvmj-47v9-35m9 is a vulnerability in fuser, published on 10 Sep 2021. 

### Official description

During the creation of a new libfuse session with `fuse_session_new`, the operation list was passed as NULL incorrectly. libfuse expects this argument to always point to list of operations. This caused uninitialized memory read and leaks in libfuse.so.

## Which versions are affected by GHSA-cvmj-47v9-35m9?

3 open source packages ship an affected version, including fuser.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fuser` | crates.io | All versions | 0.16.0 |
| `fuser` | crates.io | All versions | 0.16.0 |
| `fuser` | crates.io | From 0.0.0-0 | 0.16.0 |

## How do I fix GHSA-cvmj-47v9-35m9?

Upgrade fuser to 0.16.0 or later.

## Is GHSA-cvmj-47v9-35m9 being exploited?

There is no known exploitation of GHSA-cvmj-47v9-35m9 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-cvmj-47v9-35m9 and fix it if it is affected.

What it is: GHSA-cvmj-47v9-35m9 is a vulnerability in fuser, published on 10 Sep 2021. 
Exploitation: There is no known exploitation of GHSA-cvmj-47v9-35m9 in the wild and no public exploit code.

Affected packages and fixed versions:
- fuser (crates.io): affected all versions; fixed in 0.16.0
- fuser (crates.io): affected all versions; fixed in 0.16.0
- fuser (crates.io): affected from 0.0.0-0; fixed in 0.16.0

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/GHSA-cvmj-47v9-35m9/ (Markdown: https://insights.sbomify.com/GHSA-cvmj-47v9-35m9/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-cvmj-47v9-35m9

---
From sbomify Insights: https://insights.sbomify.com/GHSA-cvmj-47v9-35m9/
Summaries are generated and may contain mistakes; the official description above is the record.