OSV-2020-200
Heap-buffer-overflow in spng_decode_scanline
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22595
Crash type: Heap-buffer-overflow WRITE 2
Crash state:
spng_decode_scanline
spng_decode_row
spng_decode_image
What each source reports
OSV No score
Heap-buffer-overflow in spng_decode_scanline
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22595
Crash type: Heap-buffer-overflow WRITE 2
Crash state:
spng_decode_scanline
spng_decode_row
spng_decode_image
- Record
OSV-2020-200- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
libspngOSS-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-200 is a vulnerability with no CVSS score yet in libspng, published June 24, 2020. No source lists public exploit code. A source reports a fix.