CVE-2021-43620 Improper Input Validation in fruity

High 7.5 Published Updated

Attackers can bypass filename extension validation in the fruity crate due to premature string termination, potentially leading to security bypasses or data exposure.

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

What is CVE-2021-43620?

CVE-2021-43620 is a high-severity vulnerability in n/a, published on 15 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

An issue was discovered in the fruity crate through 0.2.0 for Rust. Security-relevant validation of filename extensions is plausibly affected. Methods of NSString for conversion to a string may return a partial result. Because they call CStr::from_ptr on a pointer to the string buffer, the string is terminated at the first '\0' byte, which might not be the end of the string.

Which versions are affected by CVE-2021-43620?

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

PackageAffectedFixed in
fruity crates.ioFrom 0.1.00.3.0
fruity crates.ioFrom 0.1.00.3.0
fruity crates.ioFrom 0.1.00.3.0

Products include Fruity Project Fruity.

How do I fix CVE-2021-43620?

Upgrade fruity to 0.3.0 or later.

Is CVE-2021-43620 being exploited?

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

Sources

Also known as GHSA-h352-g5vw-3926, RUSTSEC-2021-0123.

Is CVE-2021-43620 in your software?

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

Check your SBOMs for free