PatchTheCVEreload4j vulnerabilities and fixes
Recent CVEs affecting reload4j, with upgrade or downgrade steps. 4 tracked.
reload4j has 4 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 4. Most recent: 2022-01-18. Highest priority: CVE-2022-23305 (score 77/100).
- CVE-2020-9493 CRITICAL 9.8 UPGRADE UPGRADE A deserialization flaw was found in Apache Chainsaw versions prior to 2.1.0 which could lead to malicious code
- CVE-2022-23307 HIGH 8.8 UPGRADE UPGRADE CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw
- CVE-2022-23305 CRITICAL 9.8 UPGRADE MITIGATE By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the val
- CVE-2022-23302 HIGH 8.8 UPGRADE MITIGATE JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has
FAQ
How do I fix reload4j vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is reload4j being exploited right now?
None of the tracked reload4j CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which reload4j CVE should I patch first?
CVE-2022-23305 currently ranks highest (77/100): By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the val.