Apache Software Foundation Log4j 2.3.2

CPE Details

Apache Software Foundation Log4j 2.3.2
apache
log4j
2.3.2
2022-01-31
20h14 +00:00
2022-01-31
20h16 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:apache:log4j:2.3.2:-:*:*:*:*:*:*

Informations

Vendor

apache

Product

log4j

Version

2.3.2

Update

-

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2021-45046 2021-12-14 16h55 +00:00 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.
9
Critical
CVE-2017-5645 2017-04-17 19h00 +00:00 In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitrary code.
9.8
Critical