Loading vulnerability…
CVE-2022-23305 is an SQL injection vulnerability in Apache Log4j 1.2.x JDBCAppender. The appender accepts a configured SQL statement and incorporates values generated by PatternLayout converters, commonly including the message converter %m. Attacker-controlled strings submitted through application input fields or headers can alter the SQL statement when logged, causing unintended database queries to execute. Exploitation requires explicit use of JDBCAppender, which is not enabled by default.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
47 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A SQL injection vulnerability in Apache Log4j 1.2.x JDBCAppender allows attacker-controlled strings logged by an application to alter SQL statements and execute unintended queries. It requires a non-default JDBCAppender configuration. The reference assigns a CVSS v3 base score of 9.8 and reports available exploits. Log4j 1.2 reached end of life in August 2015.
An SQL-injection vulnerability in Apache Log4j 1.x applications configured to use the JDBCAppender component.
A critical, network-reachable vulnerability with no required privileges or user interaction, rated for high impact to confidentiality, integrity, and availability.
SQL-injection vulnerability in Log4j 1.x when an application is configured to use JDBCAppender.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.