What happened
SQL Injection in Apache Log4j via JDBCAppender.
Affected versions
Unknown product: See original advisory Fixed: See vendor advisory.
Why it matters
This source correlation may provide earlier visibility while structured CVE metadata is still being updated.
Detection & mitigation
- Review the original advisory and validate affected versions.
- Apply vendor-provided updates or mitigations when available.
Public PoC references
RepositoryAuthorFirst seenReference
PoC-in-GitHub · HynekPetrak/log4shell-finderFastest filesystem scanner for log4shell (CVE-2021-44228, CVE-2021-45046) and other vulnerable (CVE-2017-5645, CVE-2019-17571, CVE-2022-23305, CVE-2022-23307 ... ) instances of log4j library. Excellent performance and low memory footprint.★ 39HynekPetrak2021-12-14VerifiedPoC-in-GitHub · AlphabugX/CVE-2022-RCEtest 反向辣鸡数据投放 CVE-2022-23305 工具 利用 教程 Exploit POC★ 5AlphabugX2022-01-21CandidatePoC-in-GitHub · tkomlodi/CVE-2022-23305_POCCVE-2022-23305 Log4J JDBCAppender SQl injection POC★ 1tkomlodi2023-07-24Candidatehoor113/CVE-2022-23305-Demo-and-Whitebox-ReportSQL Injection in Apache Log4j via JDBCAppender.hoor1132026-10-17T08:56:59VerifiedSploitusSQL Injection in Apache Log4j via JDBCAppender.hoor1132026-10-17T08:56:59VerifiedSource timeline
Discovered through PoC-in-GitHubView source ↗
Record history
Record created from the first normalized source observation.
Metadata and source references refreshed.