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


Severity

Recommended
critical

Based on Amazon Linux security rating.

Threat Intelligence

Exploit Maturity
Mature
EPSS
97.29% (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-JAVA180OPENJDKACCESSIBILITY-2321931
  • published19 Dec 2021
  • disclosed14 Dec 2021

Introduced: 14 Dec 2021

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

How to fix?

Upgrade Amazon-Linux:2 java-1.8.0-openjdk-accessibility 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-accessibility package and not the java-1.8.0-openjdk-accessibility package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2 relevant fixed versions and status.

It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.

References

CVSS Scores

version 3.1