OSV-2021-396
Heap-buffer-overflow in OT::OffsetTo<OT::Anchor, OT::IntType<unsigned short, 2u>, true>* hb_serialize_co
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=30908
Crash type: Heap-buffer-overflow READ 2
Crash state:
OT::OffsetTo<OT::Anchor, OT::IntType<unsigned short, 2u>, true>* hb_serialize_co
OT::OffsetTo<OT::Anchor, OT::IntType<unsigned short, 2u>, true>* hb_serialize_co
bool OT::AnchorMatrix::serialize<hb_filter_iter_t<hb_range_iter_t<unsigned int,
What each source reports
OSV No score
Heap-buffer-overflow in OT::OffsetTo<OT::Anchor, OT::IntType<unsigned short, 2u>, true>* hb_serialize_co
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=30908
Crash type: Heap-buffer-overflow READ 2
Crash state:
OT::OffsetTo<OT::Anchor, OT::IntType<unsigned short, 2u>, true>* hb_serialize_co
OT::OffsetTo<OT::Anchor, OT::IntType<unsigned short, 2u>, true>* hb_serialize_co
bool OT::AnchorMatrix::serialize<hb_filter_iter_t<hb_range_iter_t<unsigned int,
- Record
OSV-2021-396- 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-2021-396 is a vulnerability with no CVSS score yet in harfbuzz, published February 14, 2021. No source lists public exploit code. A source reports a fix.