OSV-2020-516
Heap-buffer-overflow in hb_array_t<OT::IntType<unsigned short, 2u> const> hb_array_t<OT::IntType<unsigne
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18513
Crash type: Heap-buffer-overflow READ 2
Crash state:
hb_array_t<OT::IntType<unsigned short, 2u> const> hb_array_t<OT::IntType<unsigne
OT::UnsizedArrayOf<OT::IntType<unsigned short, 2u> >::copy
_ZN22hb_serialize_context_t5_copyIN2OT14UnsizedArrayOfINS1_7IntTypeItLj2EEEEEJRj
What each source reports
OSV No score
Heap-buffer-overflow in hb_array_t<OT::IntType<unsigned short, 2u> const> hb_array_t<OT::IntType<unsigne
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18513
Crash type: Heap-buffer-overflow READ 2
Crash state:
hb_array_t<OT::IntType<unsigned short, 2u> const> hb_array_t<OT::IntType<unsigne
OT::UnsizedArrayOf<OT::IntType<unsigned short, 2u> >::copy
_ZN22hb_serialize_context_t5_copyIN2OT14UnsizedArrayOfINS1_7IntTypeItLj2EEEEEJRj
- Record
OSV-2020-516- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
harfbuzzOSS-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-516 is a vulnerability with no CVSS score yet in harfbuzz, published July 1, 2020. No source lists public exploit code. A source reports a fix.