CVE-2021-45105 - MergeBase Vulnerability Database
Risk Score
Out of 10
Dec 18, 2021
Jul 25, 2022


Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.
MergeBase Comment

We have released a public free tool for detecting vulnerable Log4J versions within any applications that are vulnerable. Available on GitHub here:

We have also prepared a YouTube video that explains the critical CVE-2021-44228 Log4J vulnerability in detail, and shows how MergeBase can prevent attackers from exploiting this vulnerability in running unpatched production systems.

Discover More from MergeBase

Open Source Protection

Stay on top of the real risk of open source at any time.

Avoid false positives and get sophisticated upgrade guidance based on risk, compatibility and popularity.

More on Continuous Protection

Add RunTime Protection

Detect and defend against known-vulnerabilities at runtime. The only SCA to do so.

The quickest way to respond to an imminent threat like log4j with CVE-2021-44228.

More on Run-time Protection

Shift Left Now

CodeGreen is an early-warning defence for your in-house development and integrates directly into GitHub and BitBucket

More on BitBucket and Github apps