OSV-2020-1694 Segv on unknown address in std::__1::__tree<std::__1::__value_type<unsigned int, std::__1::pair<std::__1::b

Not scored Published

A segmentation fault in uWebSockets' TopicTree drain function allows remote attackers to cause a denial of service 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-2020-1694?

OSV-2020-1694 is a memory corruption vulnerability in uwebsockets, published on 4 Sep 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=25376

Crash type: Segv on unknown address
Crash state:
std::__1::__tree&lt;std::__1::__value_type&lt;unsigned int, std::__1::pair&lt;std::__1::b
uWS::TopicTree::drain
std::__1::__function::__func&lt;LLVMFuzzerTestOneInput::$_1, std::__1::allocator&lt;LL

Which versions are affected by OSV-2020-1694?

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

PackageAffectedFixed in
uwebsockets OSS-FuzzAll versionsNone

How do I fix OSV-2020-1694?

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

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

Sources

Is OSV-2020-1694 in your software?

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

Check your SBOMs for free