How severe is CVE-2021-43620?

CVE-2021-43620 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.

Is CVE-2021-43620 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (67th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2021-43620?

CVE-2021-43620 primarily affects Fruity Project Fruity. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2021-43620?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2021-43620 published?

CVE-2021-43620 was published on 2021-11-15 and last updated on 2026-06-17.

CVE-2021-43620

CVE-2021-43620 is a high-severity vulnerability in Fruity Project Fruity with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 1% (67th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Fruity Project Fruity
Published: 2021-11-15
Last modified: 2026-06-17

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.

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.
How severe is CVE-2021-43620?: CVE-2021-43620 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2021-43620 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (67th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2021-43620?: CVE-2021-43620 primarily affects Fruity Project Fruity. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2021-43620?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2021-43620 published?: CVE-2021-43620 was published on 2021-11-15 and last updated on 2026-06-17.

References

Affected products (2)

cpe:2.3:a:fruity_project:fruity:0.1.0:*:*:*:*:rust:*:*
cpe:2.3:a:fruity_project:fruity:0.2.0:*:*:*:*:rust:*:*