OSV-2020-1606 UNKNOWN READ in hb_set_digest_lowest_bits_t<unsigned long, 4u>::may_have
Not scored
Published
Check this codebase for OSV-2020-1606 and fix it if it is affected.
What it is: OSV-2020-1606 is a memory corruption vulnerability in harfbuzz, published on 14 Aug 2020.
Exploitation: There is no known exploitation of OSV-2020-1606 in the wild and no public exploit code.
Affected packages and fixed versions:
- harfbuzz (OSS-Fuzz): affected all versions; no fix listed
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/OSV-2020-1606/ (Markdown: https://insights.sbomify.com/OSV-2020-1606/index.md)
An out-of-bounds read in HarfBuzz can cause a crash when processing malformed font data, potentially leading to denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2020-1606?
OSV-2020-1606 is a memory corruption vulnerability in harfbuzz, published on 14 Aug 2020.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=24842
Crash type: UNKNOWN READ
Crash state:
hb_set_digest_lowest_bits_t<unsigned long, 4u>::may_have
hb_set_digest_combiner_t<hb_set_digest_lowest_bits_t<unsigned long, 4u>, hb_set_
OT::hb_ot_layout_lookup_accelerator_t::may_have
Which versions are affected by OSV-2020-1606?
1 open source package ship an affected version, including harfbuzz.
| Package | Affected | Fixed in |
|---|---|---|
harfbuzz OSS-Fuzz | All versions | None |
How do I fix OSV-2020-1606?
No fix has been published for OSV-2020-1606 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is OSV-2020-1606 being exploited?
There is no known exploitation of OSV-2020-1606 in the wild and no public exploit code.