Security readout for executives and security teams
This is a critical SQL injection risk in Apache Log4j 1.x, but only when an application uses the non-default JDBCAppender to write logs to a database. If attacker-controlled input is logged, crafted content can alter the configured SQL statement. Log4j 1.x is end-of-life, so replacement is the durable fix. Exposure is limited to systems running Apache Log4j 1.x with JDBCAppender explicitly configured. The component is not enabled by default. Risk rises when applications log external input into database-backed logs using PatternLayout message conversion. Treat as high-priority for legacy Java estates, especially applications writing logs to databases. The practical urgency depends on whether JDBCAppender is configured. Because Log4j 1.x is unsupported and has multiple known issues, plan replacement rather than narrow exception handling. Mitigation focus: Inventory applications and vendor products for Apache Log4j 1.x usage.; Check whether JDBCAppender is configured; prioritize those systems first.; Upgrade from Log4j 1.x to a supported Log4j 2 release..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-23305 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://logging.apache.org/log4j/1.2/index.htmlCVE reference, apache · x_refsource_MISC
- https://lists.apache.org/thread/pt6lh3pbsvxqlwlp4c5l798dv2hkc85yCVE reference, apache · x_refsource_MISC
- https://www.oracle.com/security-alerts/cpuapr2022.htmlCVE reference, apache · x_refsource_MISC
- https://security.netapp.com/advisory/ntap-20220217-0007/CVE reference, apache · x_refsource_CONFIRM
- https://www.oracle.com/security-alerts/cpujul2022.htmlCVE reference, apache · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.