OSV-2020-2099 Heap-buffer-overflow in decode_chars
Not scored
Published
Check this codebase for OSV-2020-2099 and fix it if it is affected.
What it is: OSV-2020-2099 is a memory corruption vulnerability in libass, published on 28 Oct 2020.
Exploitation: There is no known exploitation of OSV-2020-2099 in the wild and no public exploit code.
Affected packages and fixed versions:
- libass (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-2099/ (Markdown: https://insights.sbomify.com/OSV-2020-2099/index.md)
A heap-buffer-overflow in font decoding allows attackers to cause crashes or potentially execute arbitrary 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-2020-2099?
OSV-2020-2099 is a memory corruption vulnerability in libass, published on 28 Oct 2020.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26674
Crash type: Heap-buffer-overflow WRITE 1
Crash state:
decode_chars
decode_font
process_text
Which versions are affected by OSV-2020-2099?
1 open source package ship an affected version, including libass.
| Package | Affected | Fixed in |
|---|---|---|
libass OSS-Fuzz | All versions | None |
How do I fix OSV-2020-2099?
No fix has been published for OSV-2020-2099 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-2099 being exploited?
There is no known exploitation of OSV-2020-2099 in the wild and no public exploit code.