How severe is CVE-2021-42341?

CVE-2021-42341 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 none, and availability high.

Is CVE-2021-42341 being actively exploited?

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

What products are affected by CVE-2021-42341?

CVE-2021-42341 affects Openrc Project Openrc. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2021-42341?

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-42341 published?

CVE-2021-42341 was published on 2021-10-14 and last updated on 2026-06-17.

CVE-2021-42341

CVE-2021-42341 is a high-severity vulnerability in Openrc Project Openrc 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: 2% (79th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Openrc Project Openrc
Published: 2021-10-14
Last modified: 2026-06-17

Description

checkpath in OpenRC before 0.44.7 uses the direct output of strlen() to allocate strings, which does not account for the '\0' byte at the end of the string. This results in memory corruption. CVE-2021-42341 was introduced in git commit 63db2d99e730547339d1bdd28e8437999c380cae, which was introduced as part of OpenRC 0.44.0 development.

Frequently asked questions

What is CVE-2021-42341?: checkpath in OpenRC before 0.44.7 uses the direct output of strlen() to allocate strings, which does not account for the '\0' byte at the end of the string. This results in memory corruption. CVE-2021-42341 was introduced in git commit 63db2d99e730547339d1bdd28e8437999c380cae, which was introduced as part of OpenRC 0.44.0 development.
How severe is CVE-2021-42341?: CVE-2021-42341 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 none, and availability high.
Is CVE-2021-42341 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (79th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2021-42341?: CVE-2021-42341 affects Openrc Project Openrc. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2021-42341?: 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-42341 published?: CVE-2021-42341 was published on 2021-10-14 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:openrc_project:openrc:*:*:*:*:*:*:*:*

More vulnerabilities in Openrc Project Openrc

CVE-2018-21269 — Medium (CVSS 5.5): checkpath in OpenRC through 0.42.1 might allow local users to take ownership of arbitrary files because a non-terminal…

All CVEs affecting Openrc Project Openrc →