CVE-2022-32549: log injection in Sling logging

Published Jun 22, 2022
·
Updated

Apache Sling Commons Log <= 5.4.0 and Apache Sling API <= 2.25.0 are vulnerable to log injection. The ability to forge logs may allow an attacker to cover tracks by injecting fake logs and potentially corrupt log files.

Affected Software

2 affected components
Apache Sling API<=2.25.0
Apache Sling Commons Log<=5.4.0

Event History

Jun 22, 2022
CVE Published
via MITRE·02:25 PM
Data Sourced
via MITRE·02:25 PM
DescriptionWeakness

Frequently Asked Questions

1

What is the severity of CVE-2022-32549?

CVE-2022-32549 is classified as a high severity vulnerability due to its potential to allow attackers to forge logs and cover their tracks.

2

How do I fix CVE-2022-32549?

To fix CVE-2022-32549, upgrade Apache Sling API to version 2.26.0 or later and Apache Sling Commons Log to version 5.4.1 or later.

3

What types of attacks can CVE-2022-32549 facilitate?

CVE-2022-32549 can facilitate log injection attacks, potentially allowing attackers to insert fake logs into log files.

4

Which versions of Apache Sling are affected by CVE-2022-32549?

CVE-2022-32549 affects Apache Sling Commons Log versions up to 5.4.0 and Apache Sling API versions up to 2.25.0.

5

Is log integrity affected by CVE-2022-32549?

Yes, CVE-2022-32549 compromises log integrity, as attackers can inject falsified logs that may corrupt log files.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203