OSV-2020-830
Heap-buffer-overflow in CRYPTO_128_wrap
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22836
Crash type: Heap-buffer-overflow WRITE 16
Crash state:
CRYPTO_128_wrap
aes_wrap_cipher_internal
aes_wrap_cipher
What each source reports
OSV No score
Heap-buffer-overflow in CRYPTO_128_wrap
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22836
Crash type: Heap-buffer-overflow WRITE 16
Crash state:
CRYPTO_128_wrap
aes_wrap_cipher_internal
aes_wrap_cipher
- Record
OSV-2020-830- 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-830 is a vulnerability with no CVSS score yet in cryptofuzz, published July 14, 2020. No source lists public exploit code. A source reports a fix.