CVE & CISA-KEV Catalog

CVE-2021-41272

HIGHEPSS 70th pctl
7.5
CVSS v3
NVD

Description

Besu is an Ethereum client written in Java. Starting in version 21.10.0, changes in the implementation of the SHL, SHR, and SAR operations resulted in the introduction of a signed type coercion error in values that represent negative values for 32 bit signed integers. Smart contracts that ask for shifts between approximately 2 billion and 4 billion bits (nonsensical but valid values for the operation) will fail to execute and hence fail to validate. In networks where vulnerable versions are mining with other clients or non-vulnerable versions this will result in a fork and the relevant transactions will not be included in the fork. In networks where vulnerable versions are not mining (such as Rinkeby) no fork will result and the validator nodes will stop accepting blocks. In networks where only vulnerable versions are mining the relevant transaction will not be included in any blocks. When the network adds a non-vulnerable version the network will act as in the first case. Besu 21.10.2 contains a patch for this issue. Besu 21.7.4 is not vulnerable and clients can roll back to that version. There is a workaround available: Once a transaction with the relevant shift operations is included in the canonical chain, the only remediation is to make sure all nodes are on non-vulnerable versions.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityNone
IntegrityNone
AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploit Intelligence

1.42%probability of exploitation in 30 days
70thpercentile

Elevated risk: more likely to be exploited than 70% of all known CVEs.

References

Related Vulnerabilities

Other CWE-681 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2022-34169High7.581%-Fix
CVE-2009-0231High8.837%--
CVE-2016-3074Critical9.837%-Fix
CVE-2008-1721High7.523%-Fix
CVE-2017-7308High7.818%-Fix
CVE-2022-43663High8.114%--

Common questions

How do I fix CVE-2021-41272?

No published fix for CVE-2021-41272 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2021-41272 being actively exploited?

Not that we know of. CVE-2021-41272 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 1.4% is the estimated probability that it will be exploited in the next 30 days. That is higher than 70% of all scored CVEs.

How severe is CVE-2021-41272?

CVE-2021-41272 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2021-41272
CVE-2021-41272 severity badge

Markdown

[![CVE-2021-41272](https://tridentstack.com/cve/badge/CVE-2021-41272.svg)](https://tridentstack.com/cve/CVE-2021-41272)

HTML

<a href="https://tridentstack.com/cve/CVE-2021-41272"><img src="https://tridentstack.com/cve/badge/CVE-2021-41272.svg" alt="CVE-2021-41272"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.