OSV-2018-3 Heap-buffer-overflow in git__strntol64

Not scored Published

A heap-buffer-overflow in the Git library allows attackers to cause denial of service or potentially execute code via crafted 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-2018-3?

OSV-2018-3 is a memory corruption vulnerability in libgit2, published on 12 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=11194

Crash type: Heap-buffer-overflow READ 1
Crash state:
git__strntol64
git__strntol32
git_signature__parse

Which versions are affected by OSV-2018-3?

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

PackageAffectedFixed in
libgit2 OSS-FuzzAll versionsNone

How do I fix OSV-2018-3?

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

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

Sources

Is OSV-2018-3 in your software?

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

Check your SBOMs for free