OSV-2017-167 Global-buffer-overflow in vte_write_debug

Not scored Published

A global buffer overflow in the VTE library allows attackers to cause crashes or potentially execute code via malicious terminal input.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is OSV-2017-167?

OSV-2017-167 is a memory corruption vulnerability in libtsm, published on 15 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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

Crash type: Global-buffer-overflow READ 1
Crash state:
vte_write_debug
do_action
parse_data

Which versions are affected by OSV-2017-167?

1 open source package ship an affected version, including libtsm.

PackageAffectedFixed in
libtsm OSS-FuzzAll versionsNone

How do I fix OSV-2017-167?

No fix has been published for OSV-2017-167 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-2017-167 being exploited?

There is no known exploitation of OSV-2017-167 in the wild and no public exploit code.

Sources

Is OSV-2017-167 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free