OSV-2021-289 Global-buffer-overflow in vte_write_debug
Not scored
Published
Check this codebase for OSV-2021-289 and fix it if it is affected.
What it is: OSV-2021-289 is a memory corruption vulnerability in libtsm, published on 7 Feb 2021.
Exploitation: There is no known exploitation of OSV-2021-289 in the wild and no public exploit code.
Affected packages and fixed versions:
- libtsm (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-2021-289/ (Markdown: https://insights.sbomify.com/OSV-2021-289/index.md)
A global buffer overflow in the VTE terminal library's debug write function can cause a crash, affecting applications using this library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2021-289?
OSV-2021-289 is a memory corruption vulnerability in libtsm, published on 7 Feb 2021.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=30351
Crash type: Global-buffer-overflow READ 1
Crash state:
vte_write_debug
do_action
parse_data
Which versions are affected by OSV-2021-289?
1 open source package ship an affected version, including libtsm.
| Package | Affected | Fixed in |
|---|---|---|
libtsm OSS-Fuzz | All versions | None |
How do I fix OSV-2021-289?
No fix has been published for OSV-2021-289 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-2021-289 being exploited?
There is no known exploitation of OSV-2021-289 in the wild and no public exploit code.