Skip to main content
No exploitation reportedFix available

CVE-2021-43620

No exploitation reported by the sources we read.

  • Published2021-11-15
  • Fixed in0.3.0

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2021-11-1505:15CVE publishedNVD

Versions per branch

OSV · NVD
fruity
BranchAffectedFixed in
0.x≥ 0.1.0, < 0.3.00.3.0
Fruity project fruity
BranchAffectedFixed in
0.1= 0.1.0no fix published
0.2= 0.2.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update fruity to 0.3.0

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Published
2021-11-15
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-h352-g5vw-3926

Frequently asked questions

What is CVE-2021-43620?

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.

Is CVE-2021-43620 actively exploited?

Active exploitation of CVE-2021-43620 has not been confirmed. Its EPSS score was 1.4% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2021-43620?

CVE-2021-43620 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

Running fruity? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record