Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2.15 hash? #5

Open
dancing-groot opened this issue Dec 14, 2021 · 1 comment
Open

2.15 hash? #5

dancing-groot opened this issue Dec 14, 2021 · 1 comment

Comments

@dancing-groot
Copy link

Hi,

Can you add the hash for 2.15 please? It seems that 2.16 is now the recommended version:
https://logging.apache.org/log4j/2.x/security.html

@mubix
Copy link
Owner

mubix commented Dec 17, 2021

From the new CVE:

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 makes a best-effort attempt to restrict JNDI LDAP lookups to localhost by default. Log4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default.

This is a different CVE and requires a non-default configuration for logging to happen. I am not sure adding 2.15 to this list will not cause undue fear that it's exploitable at the same magnitude as the original CVE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants