Stay Informed
This week, read about:
- Log4Shell Update: Second log4j Vulnerability Published (CVE-2021-44228 + CVE-2021-45046).
- Malicious NPM Packages Are Part of a Malware “Barrage” Hitting Repositories.
- The Log4Shell 0-day, Four Days on: What is it, and How Bad is it Really?
- Commission Makes Software Available to All to Benefit Businesses, Innovators and Areas of Public Interest.
Key Security, Maintenance, and Features Releases
Security Updates
Apache Log4j 2.12.2/2.16.0
https://logging.apache.org/log4j/2.x/security.html
CVE-2021-44228 Severity Critical, CVSS SCORE 10.0: In Apache Log4j2 versions up to and including 2.14.1 (excluding security release 2.12.2), the JNDI features used in configurations, log messages, and parameters do not protect against attacker-controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled.
CVE-2021-45046 Severity Moderate, CVSS Score 3.7: 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.
Working with open source software?
Take our 10-minute survey for a chance at a $200 Amazon gift card!