Multiple vulnerabilities in Apache Log4j



Published: 2022-01-18
Risk High
Patch available YES
Number of vulnerabilities 2
CVE-ID CVE-2022-23302
CVE-2022-23305
CWE-ID CWE-502
CWE-89
Exploitation vector Network
Public exploit N/A
Vulnerable software
Subscribe
Apache Log4j
Universal components / Libraries / Libraries used by multiple products

Vendor Apache Foundation

Security Bulletin

This security bulletin contains information about 2 vulnerabilities.

1) Deserialization of Untrusted Data

EUVDB-ID: #VU59692

Risk: High

CVSSv3.1:

CVE-ID: CVE-2022-23302

CWE-ID: CWE-502 - Deserialization of Untrusted Data

Exploit availability: No

Description

The vulnerability allows a remote attacker to execute arbitrary code on the target system.

The vulnerability exists due to insecure input validation when processing serialized data in JMSSink. A remote attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests and execute arbitrary code on the target system.

Note, a non-default configuration with support for JMSSink is required to exploit this vulnerability.

Mitigation

Upgrade Apache Log4j to the 2.x branch.

Vulnerable software versions

Apache Log4j: 1.0.4 - 1.2.17


CPE2.3 External links

http://lists.apache.org/thread/bsr3l5qz4g0myrjhy9h67bcxodpkwj4w
http://logging.apache.org/log4j/1.2/index.html

Q & A

Can this vulnerability be exploited remotely?

Is there known malware, which exploits this vulnerability?

2) SQL injection

EUVDB-ID: #VU59691

Risk: Medium

CVSSv3.1:

CVE-ID: CVE-2022-23305

CWE-ID: CWE-89 - Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Exploit availability: No

Description

The vulnerability allows a remote attacker to execute arbitrary SQL queries in database.

The vulnerability exists due to insufficient sanitization of user-supplied data in the JDBCAppender. A remote attacker can send a specially crafted request to the affected application and execute arbitrary SQL commands within the application database.

Note, a non-default configuration with enabled JDBCAppender is required to exploit the vulnerability.

Mitigation

The vulnerability is resolved in Apache Log4j 2.x branch.

Vulnerable software versions

Apache Log4j: 1.2.1 - 1.2.17


CPE2.3 External links

http://lists.apache.org/thread/pt6lh3pbsvxqlwlp4c5l798dv2hkc85y
http://logging.apache.org/log4j/1.2/index.html

Q & A

Can this vulnerability be exploited remotely?

Is there known malware, which exploits this vulnerability?



###SIDEBAR###