Non notée
CVE-2022-23302 JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write…
Description
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
Produits et versions touchés
| Produit | Versions touchées | Corrigé en |
|---|---|---|
| Apache Log4j 1.x 2.0 | premières → < 2.0-alpha1 | 2.0-alpha1 |
| Apache Log4j 1.x 1.0 | 1.0.1 → dernières | Pas de correctif indiqué |
Références
- lists.apache.org lists.apache.org
- logging.apache.org logging.apache.org
- [oss-security] 20220118 CVE-2022-23302: Deserialization of untrusted data in JMSSink in Apache Log4j 1.x www.openwall.com
- www.oracle.com www.oracle.com
- security.netapp.com security.netapp.com
- www.oracle.com www.oracle.com
Chronologie
- Publiée
- Dernière modification
Autres CVE de Apache Log4j 1.x
Les 4 CVE de Apache Log4j 1.x →
CVE-2022-23307
CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw
Non notée
CVE-2022-23305
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to…
Non notée
CVE-2021-4104
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the…
7.5
Élevée