CVE-2022-23305

Aliases:GHSA-65fg-84f6-3jq3
Modified
Published: 18 Jan 2022, 15:25
Last modified:27 May 2026, 13:40

Vulnerability Summary

Overall Risk (default)
high
70/100
CVSS Score
9.8 CRITICAL
v3.1 (nvd)
EPSS Score
9.45% LOW
9% probability +1.50%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

18 Jan 2022, 15:25
Published
Vulnerability first disclosed
27 May 2026, 13:40
Last Modified
Vulnerability information updated

Description

By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.

CVSS Metrics

  • v3.1CRITICALScore: 9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • v2.0MEDIUMScore: 6.8AV:N/AC:M/Au:N/C:P/I:P/A:P

EPSS Trends

Current EPSS score: 9.45% Percentile: 93%

Techniques & Countermeasures

  • CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

    The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Affected Systems

  • apache software foundationapache log4j 1.x

    ≥ 1.2.1, < unspecified | ≥ unspecified, < 2.0-alpha1

  • apachelog4j

    ≥ 1.2, ≤ 1.2.17

  • broadcombrocade_sannav

    na

  • log4jlog4j

    ≤ 1.2.17

  • org.zenframework.z8.dependencies.commonslog4j-1.2.17

    ≤ 2.0

  • netappsnapmanager

    na

  • oracleadvanced_supply_chain_planning

    12.1 | 12.2

  • oraclebusiness_intelligence

    5.9.0.0.0 | 12.2.1.3.0 | 12.2.1.4.0

  • oraclebusiness_process_management_suite

    12.2.1.3.0 | 12.2.1.4.0

  • oraclecommunications_eagle_ftp_table_base_retrieval

    4.5

  • oraclecommunications_instant_messaging_server

    10.0.1.5.0

  • oraclecommunications_messaging_server

    8.1

  • oraclecommunications_network_integrity

    7.3.6

  • oraclecommunications_offline_mediation_controller

    < 12.0.0.4.4 | 12.0.0.5.0

  • oraclecommunications_unified_inventory_management

    7.4.1 | 7.4.2

  • oraclee-business_suite_cloud_manager_and_cloud_backup_module

    < 2.2.1.1.1 | 2.2.1.1.1

  • oraclee-business_suite_information_discovery

    ≥ 12.2.3, ≤ 12.2.11

  • oracleenterprise_manager_base_platform

    13.4.0.0 | 13.5.0.0

  • oraclefinancial_services_revenue_management_and_billing_analytics

    2.7.0.0 | 2.7.0.1 | 2.8.0.0

  • oraclehealthcare_foundation

    8.1.0

  • oraclehyperion_data_relationship_management

    < 11.2.8.0

  • oraclehyperion_infrastructure_technology

    < 11.2.8.0

  • oracleidentity_management_suite

    12.2.1.3.0 | 12.2.1.4.0

  • oracleidentity_manager_connector

    11.1.1.5.0

  • oraclejdeveloper

    12.2.1.3.0

  • oraclemiddleware_common_libraries_and_tools

    12.2.1.4.0

  • oraclemysql_enterprise_monitor

    ≤ 8.0.29

  • oracleretail_extract_transform_and_load

    13.2.5

  • oracletuxedo

    12.2.2.0.0

  • UnknownWebLogic Server

    12.2.1.3.0 | 12.2.1.4.0 | 14.1.1.0.0

  • qosreload4j

    < 1.2.18.2

References (9)