OSV-2020-388
Stack-use-after-return in bool OT::Coverage::serialize<hb_map_iter_t<hb_map_iter_t<hb_filter_iter_t<OT::Co
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14786
Crash type: Stack-use-after-return READ 4
Crash state:
bool OT::Coverage::serialize<hb_map_iter_t<hb_map_iter_t<hb_filter_iter_t<OT::Co
bool OT::SingleSubstFormat1::serialize<hb_map_iter_t<hb_map_iter_t<hb_filter_ite
bool OT::SingleSubst::serialize<hb_map_iter_t<hb_filter_iter_t<OT::Coverage::ite
What each source reports
OSV No score
Stack-use-after-return in bool OT::Coverage::serialize<hb_map_iter_t<hb_map_iter_t<hb_filter_iter_t<OT::Co
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14786
Crash type: Stack-use-after-return READ 4
Crash state:
bool OT::Coverage::serialize<hb_map_iter_t<hb_map_iter_t<hb_filter_iter_t<OT::Co
bool OT::SingleSubstFormat1::serialize<hb_map_iter_t<hb_map_iter_t<hb_filter_ite
bool OT::SingleSubst::serialize<hb_map_iter_t<hb_filter_iter_t<OT::Coverage::ite
- Record
OSV-2020-388- 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-388 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.