OSV-2020-201
Use-of-uninitialized-value in fuzzing::memory::memory_test_msan
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22453
Crash type: Use-of-uninitialized-value
Crash state:
fuzzing::memory::memory_test_msan
cryptofuzz::ExecutorBase<cryptofuzz::Buffer, cryptofuzz::operation::CMAC>::postp
cryptofuzz::ExecutorBase<cryptofuzz::Buffer, cryptofuzz::operation::CMAC>::Run
What each source reports
OSV No score
Use-of-uninitialized-value in fuzzing::memory::memory_test_msan
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22453
Crash type: Use-of-uninitialized-value
Crash state:
fuzzing::memory::memory_test_msan
cryptofuzz::ExecutorBase<cryptofuzz::Buffer, cryptofuzz::operation::CMAC>::postp
cryptofuzz::ExecutorBase<cryptofuzz::Buffer, cryptofuzz::operation::CMAC>::Run
- Record
OSV-2020-201- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
cryptofuzzOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2020-201 is a vulnerability with no CVSS score yet in cryptofuzz, published June 24, 2020. No source lists public exploit code. A source reports a fix.