OSV-2018-64
Heap-buffer-overflow in BEInt<unsigned int, 4>::operator unsigned int
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11522
Crash type: Heap-buffer-overflow READ 1
Crash state:
BEInt<unsigned int, 4>::operator unsigned int
void hb_sanitize_context_t::set_object<OT::KernSubTable<OT::KernAATSubTableHeade
AAT::KerxTable<OT::KernAAT>::sanitize
What each source reports
OSV No score
Heap-buffer-overflow in BEInt<unsigned int, 4>::operator unsigned int
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11522
Crash type: Heap-buffer-overflow READ 1
Crash state:
BEInt<unsigned int, 4>::operator unsigned int
void hb_sanitize_context_t::set_object<OT::KernSubTable<OT::KernAATSubTableHeade
AAT::KerxTable<OT::KernAAT>::sanitize
- Record
OSV-2018-64- 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-2018-64 is a vulnerability with no CVSS score yet in harfbuzz, published January 13, 2021. No source lists public exploit code. A source reports a fix.