LOWcrates.io →
cap-std doesn't fully sandbox all the Windows device filenames
cap-std doesn't fully sandbox all the Windows device filenames
Affected packages
- cap-async-std
- cap-primitives
- cap-std
Exploit signal
- Known exploited (CISA KEV)
- No
- EPSS score
- —
- EPSS percentile
- —
EPSS is the probability a CVE is exploited in the wild; percentile is its rank among all CVEs.
Sources
- https://github.com/bytecodealliance/cap-std/security/advisories/GHSA-hxf5-99xg-86hw
- https://nvd.nist.gov/vuln/detail/CVE-2024-51756
- https://github.com/bytecodealliance/cap-std/pull/371
- https://github.com/bytecodealliance/cap-std/commit/dcc3818039761331fbeacbb3a40c542b65b5ebf7
- https://en.wikipedia.org/wiki/ISO/IEC_8859-1
- https://github.com/bytecodealliance/cap-std
- https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions
- https://rustsec.org/advisories/RUSTSEC-2024-0445.html
Structured record: https://osv.dev/vulnerability/GHSA-hxf5-99xg-86hw
Recommended response stack
Some links are affiliate links — HackTribune may earn a commission at no extra cost to you.
Get incidents like this as alerts for your stack.
Join the beta