GHSA-cvmj-47v9-35m9 json
FUSE-Rust: Uninitalized memory read and leak caused by fuser crate
published 5y ago modified last yr. also RUSTSEC-2021-0154
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- crates.io fuser 0.16.0
- github.com/cberner/fuser#390 pull request
- github.com/libfuse/libfuse#1330 pull request
Is GHSA-cvmj-47v9-35m9 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | fuser | <0.16.0 >=0.0.0-0, <0.16.0 |
0.16.0 |
Classification
- Weakness
-
- CWE-908 Use of Uninitialized Resource
References
-
github.com
/cberner/fuser/pull/390
web
-
github.com
/libfuse/libfuse/pull/1330
web
-
github.com
/cberner/fuser
package
-
rustsec.org
/advisories/RUSTSEC-2021-0154.html
web, advisory
-
crates.io
/crates/fuser
package
Sources
- GitHub Advisory GHSA-cvmj-47v9-35m9
- OSV RUSTSEC-2021-0154
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.