One Article Review
| Source |  CVE Liste |
|---|---|
| Identifiant | 3796753 |
| Date de publication | 2021-12-14 19:15:07 (vue: 2021-12-14 22:06:35) |
| Titre | CVE-2021-45046 |
| Texte | 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 a denial of service (DOS) attack. Log4j 2.15.0 restricts JNDI LDAP lookups to localhost by default. Note that previous mitigations involving configuration such as to set the system property `log4j2.noFormatMsgLookup` to `true` do NOT mitigate this specific vulnerability. Log4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases ( |
| Envoyé | Oui |
| Condensat | 2021 44228 45046 `log4j2 `true` address allows apache attack attackers can certain class classpath configuration configurations context control core could craft ctx:loginid cve data default denial disabling dos either example example: fix fixes found from functionality incomplete input involving issue jar jndi jndilookup layout ldap localhost log4j logging lookup lookups malicious map mdc message mitigate mitigated mitigations noformatmsglookup` non not note org/apache/logging/log4j/core/lookup/jndilookup over pattern patterns previous prior property releases removing restricts resulting service set specific such support system thread uses using vulnerability when zip |
| Tags | |
| Stories | |
| Notes | |
| Move | 
|
L'article ne semble pas avoir été repris aprés sa publication.
L'article ne semble pas avoir été repris sur un précédent.