OSV-2020-372
Heap-buffer-overflow in circular_memcpy
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13435
Crash type: Heap-buffer-overflow READ {*}
Crash state:
circular_memcpy
run_e8e9_filter
run_filter
What each source reports
OSV No score
Heap-buffer-overflow in circular_memcpy
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13435
Crash type: Heap-buffer-overflow READ {*}
Crash state:
circular_memcpy
run_e8e9_filter
run_filter
- Record
OSV-2020-372- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
libarchiveOSS-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-372 is a vulnerability with no CVSS score yet in libarchive, published July 1, 2020. No source lists public exploit code. A source reports a fix.