Every CVE Search/ Get API key

OSV-2023-377

UNKNOWN WRITE in bool OT::Layout::Common::CoverageFormat2_4<OT::Layout::MediumTypes>::serialize<h

No scoreFix available

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=58671

Crash type: UNKNOWN WRITE
Crash state:
bool OT::Layout::Common::CoverageFormat2_4<OT::Layout::MediumTypes>::serialize<h
bool OT::Layout::Common::Coverage::serialize<hb_sorted_array_t<unsigned int cons
OT::Layout::GSUB_impl::AlternateSubstFormat1_2<OT::Layout::SmallTypes>::subset

What each source reports

OSV No score

UNKNOWN WRITE in bool OT::Layout::Common::CoverageFormat2_4<OT::Layout::MediumTypes>::serialize<h

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=58671

Crash type: UNKNOWN WRITE
Crash state:
bool OT::Layout::Common::CoverageFormat2_4<OT::Layout::MediumTypes>::serialize<h
bool OT::Layout::Common::Coverage::serialize<hb_sorted_array_t<unsigned int cons
OT::Layout::GSUB_impl::AlternateSubstFormat1_2<OT::Layout::SmallTypes>::subset
Record
OSV-2023-377
Updated
2026-11-02

Affected packages

Affected packages
PackageAffectedFixed
harfbuzz
OSS-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

History
RecordedChangedSources
first indexedOSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

OSV-2023-377 is a vulnerability with no CVSS score yet in harfbuzz, published May 7, 2023. No source lists public exploit code. A source reports a fix.

References

MoveEnter Open