CVE-2020-36205 Memory handling issues in xcb

Medium 5.5 Published Updated

A use-after-free or double-free vulnerability in the Rust xcb crate allows attackers to potentially execute arbitrary code or cause a denial of service.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2020-36205?

CVE-2020-36205 is a medium-severity use after free vulnerability in n/a, published on 22 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur.

Weakness: CWE-416, CWE-415

Which versions are affected by CVE-2020-36205?

3 open source packages ship an affected version, including xcb. It affects 1 product.

PackageAffectedFixed in
xcb crates.ioAll versions1.0.0
xcb crates.ioAll versions1.0.0
xcb crates.ioFrom 0.0.0-01.0.0

Products include Xcb Project Xcb.

How do I fix CVE-2020-36205?

Upgrade xcb to 1.0.0 or later.

Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.

Is CVE-2020-36205 being exploited?

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

Sources

Also known as DEBIAN-CVE-2020-36205, GHSA-c8hq-x4mm-p6q6, RUSTSEC-2020-0097, UBUNTU-CVE-2020-36205.

Is CVE-2020-36205 in your software?

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

Check your SBOMs for free