What is the severity of ZDI-CAN-16160?

The severity of ZDI-CAN-16160 is critical due to its ability to enable remote denial-of-service attacks.

How do I fix ZDI-CAN-16160?

To fix ZDI-CAN-16160, update the Apache Log4j to the latest version that addresses this vulnerability.

What types of installations are affected by ZDI-CAN-16160?

ZDI-CAN-16160 affects all installations of Apache Log4j that utilize the StrSubstitutor class.

Is authentication required to exploit ZDI-CAN-16160?

No, authentication is not required to exploit ZDI-CAN-16160, making it particularly dangerous.

What are the potential impacts of ZDI-CAN-16160?

The potential impact of ZDI-CAN-16160 includes causing a denial-of-service condition leading to application downtime.

Vulnerability/
ZDI-CAN-16160

medium

5.3

4/8/2024

ZDI-CAN-16160: Apache Log4j StrSubstitutor Uncontrolled Recursion Denial-of-Service Vulnerability

This vulnerability allows remote attackers to create a denial-of-service condition on affected installations of Apache Log4j. Authentication is not required to exploit this vulnerability. The specific flaw exists within the StrSubstitutor class. The issue results from the lack of proper validation of user-supplied data, which can result in a resource exhaustion condition. An attacker can leverage this vulnerability to create a denial-of-service condition on the process.

Affected Software	Affected Version	How to fix
Apache Log4j

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of ZDI-CAN-16160?
The severity of ZDI-CAN-16160 is critical due to its ability to enable remote denial-of-service attacks.
How do I fix ZDI-CAN-16160?
To fix ZDI-CAN-16160, update the Apache Log4j to the latest version that addresses this vulnerability.
What types of installations are affected by ZDI-CAN-16160?
ZDI-CAN-16160 affects all installations of Apache Log4j that utilize the StrSubstitutor class.
Is authentication required to exploit ZDI-CAN-16160?
No, authentication is not required to exploit ZDI-CAN-16160, making it particularly dangerous.
What are the potential impacts of ZDI-CAN-16160?
The potential impact of ZDI-CAN-16160 includes causing a denial-of-service condition leading to application downtime.

agent/references
agent/softwarecombine
collector/zdi-advisory
source/ZDI
alias/ZDI-21-1541
alias/ZDI-CAN-16160
alias/CVE-2021-45105
agent/software-canonical-lookup
agent/severity
agent/title
agent/type
agent/description
agent/event
agent/tags
agent/source
vendor/apache
canonical/apache log4j

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of ZDI-CAN-16160?
The severity of ZDI-CAN-16160 is critical due to its ability to enable remote denial-of-service attacks.
How do I fix ZDI-CAN-16160?
To fix ZDI-CAN-16160, update the Apache Log4j to the latest version that addresses this vulnerability.
What types of installations are affected by ZDI-CAN-16160?
ZDI-CAN-16160 affects all installations of Apache Log4j that utilize the StrSubstitutor class.
Is authentication required to exploit ZDI-CAN-16160?
No, authentication is not required to exploit ZDI-CAN-16160, making it particularly dangerous.
What are the potential impacts of ZDI-CAN-16160?
The potential impact of ZDI-CAN-16160 includes causing a denial-of-service condition leading to application downtime.