OSV-2018-100 Heap-buffer-overflow in cff_parser_run
Not scored
Published
Check this codebase for OSV-2018-100 and fix it if it is affected.
What it is: OSV-2018-100 is a memory corruption vulnerability in freetype2, published on 13 Jan 2021.
Exploitation: There is no known exploitation of OSV-2018-100 in the wild and no public exploit code.
Affected packages and fixed versions:
- freetype2 (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-2018-100/ (Markdown: https://insights.sbomify.com/OSV-2018-100/index.md)
A heap buffer overflow in the CFF parser allows attackers to cause crashes or potentially execute code via malicious font files.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2018-100?
OSV-2018-100 is a memory corruption vulnerability in freetype2, published on 13 Jan 2021.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10869
Crash type: Heap-buffer-overflow WRITE 1
Crash state:
cff_parser_run
cff_subfont_load
cff_font_load
Which versions are affected by OSV-2018-100?
1 open source package ship an affected version, including freetype2.
| Package | Affected | Fixed in |
|---|---|---|
freetype2 OSS-Fuzz | All versions | None |
How do I fix OSV-2018-100?
No fix has been published for OSV-2018-100 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-2018-100 being exploited?
There is no known exploitation of OSV-2018-100 in the wild and no public exploit code.