Deserialization of Untrusted Data Affecting java-1.8.0-openjdk-javadoc package, versions <1:1.8.0.312.b07-1.amzn2.0.2


Severity

Recommended
0.0
critical
0
10

Based on Amazon Linux security rating.

Threat Intelligence

Exploit Maturity
Mature
EPSS
96.89% (100th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Deserialization of Untrusted Data vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-AMZN2-JAVA180OPENJDKJAVADOC-2321930
  • published19 Dec 2021
  • disclosed10 Dec 2021

Introduced: 10 Dec 2021

CVE-2021-44228  (opens in a new tab)
CWE-502  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2 java-1.8.0-openjdk-javadoc to version 1:1.8.0.312.b07-1.amzn2.0.2 or higher.
This issue was patched in ALAS2-2021-1731.

NVD Description

Note: Versions mentioned in the description apply only to the upstream java-1.8.0-openjdk-javadoc package and not the java-1.8.0-openjdk-javadoc package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2 relevant fixed versions and status.

Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.

References

CVSS Scores

version 3.1