What is the CVSS score of CVE-2022-23305?

CVE-2022-23305 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 9.5%.

Is there a patch available for CVE-2022-23305?

Yes, a patch is available for CVE-2022-23305. Update the affected software to the latest version immediately.

Log4J CVE-2022-23305

CRITICAL

SQL Injection (CWE-89)

2022-01-18 security@apache.org

GHSA-65fg-84f6-3jq3

Apache SQLi Log4J Snapmanager Brocade Sannav Reload4J Advanced Supply Chain Planning Business Intelligence Business Process Management Suite Communications Eagle Ftp Table Base Retrieval Communications Instant Messaging Server Communications Messaging Server Communications Network Integrity Communications Offline Mediation Controller Communications Unified Inventory Management E Business Suite Cloud Manager And Cloud Backup Module E Business Suite Information Discovery Enterprise Manager Base Platform Financial Services Revenue Management And Billing Analytics Healthcare Foundation Hyperion Data Relationship Management Hyperion Infrastructure Technology Identity Management Suite Identity Manager Connector Jdeveloper Middleware Common Libraries And Tools Mysql Enterprise Monitor Retail Extract Transform And Load Tuxedo Weblogic Server

9.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Jan 18, 2022 - 16:15 cve.org

CRITICAL 9.8

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

30,810 maven packages depend on log4j:log4j (7,820 direct, 23,828 indirect)
1 maven packages depend on org.zenframework.z8.dependencies.commons:log4j-1.2.17 (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 1.2.17 and other introduced versions.

DescriptionCVE.org

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.

AnalysisAI

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. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. This SQL Injection vulnerability could allow attackers to execute arbitrary SQL commands against the database.

Technical ContextAI

This vulnerability is classified as SQL Injection (CWE-89), which allows attackers to execute arbitrary SQL commands against the database. 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. Affected products include: Apache Log4J, Netapp Snapmanager, Broadcom Brocade Sannav, Qos Reload4J, Oracle Advanced Supply Chain Planning. Version information: version 2.0.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Use parameterized queries/prepared statements. Never concatenate user input into SQL. Apply least-privilege database permissions.