GHSA-466c-pfvv-v83g json
wrflib has a soundness issue and is unmaintained
published last yr. modified last yr. also RUSTSEC-2025-0072
- 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
All functions under `wrflib::byte_extract` are simply wrapper of unsafe pointer offset and lacks sufficient checks to it pointer and offset parameter.
`wrflib` is unmaintained.
Is GHSA-466c-pfvv-v83g 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 | wrflib | <=0.0.3 >=0.0.0-0 |
no fix listed |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
github.com
/cruise-automation/webviz-rust-framework
package, web
-
rustsec.org
/advisories/RUSTSEC-2025-0072.html
web, advisory
-
crates.io
/crates/wrflib
package
Sources
- GitHub Advisory GHSA-466c-pfvv-v83g
- OSV RUSTSEC-2025-0072
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.