OSV-2020-149
Heap-buffer-overflow in BEInt<unsigned short, 2>::operator=
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21580
Crash type: Heap-buffer-overflow WRITE 1
Crash state:
BEInt<unsigned short, 2>::operator=
OT::IntType<unsigned short, 2u>::operator=
bool OT::ClassDefFormat1::serialize<hb_zip_iter_t<hb_sorted_array_t<OT::HBGlyphI
What each source reports
OSV No score
Heap-buffer-overflow in BEInt<unsigned short, 2>::operator=
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21580
Crash type: Heap-buffer-overflow WRITE 1
Crash state:
BEInt<unsigned short, 2>::operator=
OT::IntType<unsigned short, 2u>::operator=
bool OT::ClassDefFormat1::serialize<hb_zip_iter_t<hb_sorted_array_t<OT::HBGlyphI
- Record
OSV-2020-149- 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-149 is a vulnerability with no CVSS score yet in harfbuzz, published June 24, 2020. No source lists public exploit code. A source reports a fix.