Advisory

USN-5998-1

Also known as: CVE-2019-17571, CVE-2022-23302, CVE-2022-23305, CVE-2022-23307

Summary

apache-log4j1.2 vulnerabilities

Details

It was discovered that the SocketServer component of Apache Log4j 1.2
incorrectly handled deserialization. An attacker could possibly use this issue
to execute arbitrary code. This issue only affected Ubuntu 16.04 ESM.
(CVE-2019-17571)

It was discovered that the JMSSink component of Apache Log4j 1.2 incorrectly
handled deserialization. An attacker could possibly use this issue to execute
arbitrary code. (CVE-2022-23302)

It was discovered that Apache Log4j 1.2 incorrectly handled certain SQL
statements. A remote attacker could possibly use this issue to perform an SQL
injection attack and alter the database. This issue was only fixed in Ubuntu
18.04 LTS and Ubuntu 20.04 LTS. (CVE-2022-23305)

It was discovered that the Chainsaw component of Apache Log4j 1.2 incorrectly
handled deserialization. An attacker could possibly use this issue to execute
arbitrary code. This issue was only fixed in Ubuntu 18.04 LTS and Ubuntu 20.04
LTS. (CVE-2022-23307)

Severity

Not rated by the source.

Dates

Published
2023-04-05 21:26 UTC
Modified
2026-06-25 13:31 UTC

Affected packages and fixes

apache-log4j1.2

Debian packages (deb) · Ubuntu 18.04

Affected

  • introduced 0, fixed 1.2.17-8+deb10u1ubuntu0.2 (ecosystem)

Fixed versions

1.2.17-8+deb10u1ubuntu0.2

Fix

  • Fixed version 1.2.17-8+deb10u1ubuntu0.2
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

apache-log4j1.2

Debian packages (deb) · Ubuntu 20.04

Affected

  • introduced 0, fixed 1.2.17-9ubuntu0.2 (ecosystem)

Fixed versions

1.2.17-9ubuntu0.2

Fix

  • Fixed version 1.2.17-9ubuntu0.2
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: Ubuntu Security Notices · CC BY-SA 4.0

Sources & licences