OSV-2020-278 Heap-buffer-overflow in ih264d_decode_slice_thread

Not scored Published

A heap buffer overflow in the H.264 decoder allows attackers to cause crashes or potentially execute code via malicious video files.

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-2020-278?

OSV-2020-278 is a memory corruption vulnerability in libavc, published on 30 Jun 2020. 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=19027

Crash type: Heap-buffer-overflow READ 4
Crash state:
ih264d_decode_slice_thread
ih264d_decode_picture_thread
clone

Which versions are affected by OSV-2020-278?

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

PackageAffectedFixed in
libavc OSS-FuzzAll versionsNone

How do I fix OSV-2020-278?

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

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

Sources

Is OSV-2020-278 in your software?

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

Check your SBOMs for free