Your submission was sent successfully! Close

You have successfully unsubscribed! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates about Ubuntu and upcoming events where you can meet our team.Close

CVE-2022-23305

Published: 18 January 2022

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.

Priority

Medium

Cvss 3 Severity Score

9.8

Score breakdown

Status

Package Release Status
apache-log4j1.2
Launchpad, Ubuntu, Debian
bionic
Released (1.2.17-8+deb10u1ubuntu0.2)
focal
Released (1.2.17-9ubuntu0.2)
impish Ignored
(end of life)
jammy Not vulnerable
(1.2.17-11)
kinetic Not vulnerable
(1.2.17-11)
lunar Ignored
(end of life, was needs-triage)
mantic Needs triage

noble Needs triage

trusty Needs triage

upstream Needs triage

xenial
Released (1.2.17-7ubuntu1+esm1)
Available with Ubuntu Pro

Severity score breakdown

Parameter Value
Base score 9.8
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Scope Unchanged
Confidentiality High
Integrity impact High
Availability impact High
Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H