OSV-2020-1567
Heap-buffer-overflow in allocate_field
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=24580
Crash type: Heap-buffer-overflow WRITE 8
Crash state:
allocate_field
decode_pointer_field
decode_field
What each source reports
OSV No score
Heap-buffer-overflow in allocate_field
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=24580
Crash type: Heap-buffer-overflow WRITE 8
Crash state:
allocate_field
decode_pointer_field
decode_field
- Record
OSV-2020-1567- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
nanopbOSS-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-1567 is a vulnerability with no CVSS score yet in nanopb, published August 2, 2020. No source lists public exploit code. A source reports a fix.