Register | Log in

log4cxx

Choose email to subscribe with

general

source: log4cxx (main)
version: 1.4.0-1
maintainer: Tobias Frost (DMD) (LowNMU)
arch: all any
std-ver: 4.7.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 0.11.0-2
oldstable: 1.0.0-1
stable: 1.4.0-1
testing: 1.4.0-1
unstable: 1.4.0-1

versioned links

0.11.0-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.0.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.4.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

liblog4cxx-dev
liblog4cxx-doc
liblog4cxx15

action needed

A new upstream version is available: 1.5.0 high

A new upstream version 1.5.0 is available, you should consider packaging it.

Created: 2025-08-05 Last update: 2025-08-30 08:30

2 security issues in trixie high

There are 2 open security issues in trixie.

2 important issues:

CVE-2025-54812: Improper Output Neutralization for Logs vulnerability in Apache Log4cxx. When using HTMLLayout, logger names are not properly escaped when writing out to the HTML file. If untrusted data is used to retrieve the name of a logger, an attacker could theoretically inject HTML or Javascript in order to hide information from logs or steal data from the user. In order to activate this, the following sequence must occur: * Log4cxx is configured to use HTMLLayout. * Logger name comes from an untrusted string * Logger with compromised name logs a message * User opens the generated HTML log file in their browser, leading to potential XSS Because logger names are generally constant strings, we assess the impact to users as LOW This issue affects Apache Log4cxx: before 1.5.0. Users are recommended to upgrade to version 1.5.0, which fixes the issue.
CVE-2025-54813: Improper Output Neutralization for Logs vulnerability in Apache Log4cxx. When using JSONLayout, not all payload bytes are properly escaped. If an attacker-supplied message contains certain non-printable characters, these will be passed along in the message and written out as part of the JSON message. This may prevent applications that consume these logs from correctly interpreting the information within them. This issue affects Apache Log4cxx: before 1.5.0. Users are recommended to upgrade to version 1.5.0, which fixes the issue.

Created: 2025-08-22 Last update: 2025-08-23 12:00

2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:

CVE-2025-54812: Improper Output Neutralization for Logs vulnerability in Apache Log4cxx. When using HTMLLayout, logger names are not properly escaped when writing out to the HTML file. If untrusted data is used to retrieve the name of a logger, an attacker could theoretically inject HTML or Javascript in order to hide information from logs or steal data from the user. In order to activate this, the following sequence must occur: * Log4cxx is configured to use HTMLLayout. * Logger name comes from an untrusted string * Logger with compromised name logs a message * User opens the generated HTML log file in their browser, leading to potential XSS Because logger names are generally constant strings, we assess the impact to users as LOW This issue affects Apache Log4cxx: before 1.5.0. Users are recommended to upgrade to version 1.5.0, which fixes the issue.
CVE-2025-54813: Improper Output Neutralization for Logs vulnerability in Apache Log4cxx. When using JSONLayout, not all payload bytes are properly escaped. If an attacker-supplied message contains certain non-printable characters, these will be passed along in the message and written out as part of the JSON message. This may prevent applications that consume these logs from correctly interpreting the information within them. This issue affects Apache Log4cxx: before 1.5.0. Users are recommended to upgrade to version 1.5.0, which fixes the issue.

Created: 2025-08-22 Last update: 2025-08-23 12:00

2 security issues in forky high

There are 2 open security issues in forky.

2 important issues:

CVE-2025-54812: Improper Output Neutralization for Logs vulnerability in Apache Log4cxx. When using HTMLLayout, logger names are not properly escaped when writing out to the HTML file. If untrusted data is used to retrieve the name of a logger, an attacker could theoretically inject HTML or Javascript in order to hide information from logs or steal data from the user. In order to activate this, the following sequence must occur: * Log4cxx is configured to use HTMLLayout. * Logger name comes from an untrusted string * Logger with compromised name logs a message * User opens the generated HTML log file in their browser, leading to potential XSS Because logger names are generally constant strings, we assess the impact to users as LOW This issue affects Apache Log4cxx: before 1.5.0. Users are recommended to upgrade to version 1.5.0, which fixes the issue.
CVE-2025-54813: Improper Output Neutralization for Logs vulnerability in Apache Log4cxx. When using JSONLayout, not all payload bytes are properly escaped. If an attacker-supplied message contains certain non-printable characters, these will be passed along in the message and written out as part of the JSON message. This may prevent applications that consume these logs from correctly interpreting the information within them. This issue affects Apache Log4cxx: before 1.5.0. Users are recommended to upgrade to version 1.5.0, which fixes the issue.

Created: 2025-08-22 Last update: 2025-08-23 12:00

2 security issues in bullseye high

There are 2 open security issues in bullseye.

2 important issues:

CVE-2025-54812: Improper Output Neutralization for Logs vulnerability in Apache Log4cxx. When using HTMLLayout, logger names are not properly escaped when writing out to the HTML file. If untrusted data is used to retrieve the name of a logger, an attacker could theoretically inject HTML or Javascript in order to hide information from logs or steal data from the user. In order to activate this, the following sequence must occur: * Log4cxx is configured to use HTMLLayout. * Logger name comes from an untrusted string * Logger with compromised name logs a message * User opens the generated HTML log file in their browser, leading to potential XSS Because logger names are generally constant strings, we assess the impact to users as LOW This issue affects Apache Log4cxx: before 1.5.0. Users are recommended to upgrade to version 1.5.0, which fixes the issue.
CVE-2025-54813: Improper Output Neutralization for Logs vulnerability in Apache Log4cxx. When using JSONLayout, not all payload bytes are properly escaped. If an attacker-supplied message contains certain non-printable characters, these will be passed along in the message and written out as part of the JSON message. This may prevent applications that consume these logs from correctly interpreting the information within them. This issue affects Apache Log4cxx: before 1.5.0. Users are recommended to upgrade to version 1.5.0, which fixes the issue.

Created: 2025-08-22 Last update: 2025-08-23 12:00

2 security issues in bookworm high

There are 2 open security issues in bookworm.

2 important issues:

CVE-2025-54812: Improper Output Neutralization for Logs vulnerability in Apache Log4cxx. When using HTMLLayout, logger names are not properly escaped when writing out to the HTML file. If untrusted data is used to retrieve the name of a logger, an attacker could theoretically inject HTML or Javascript in order to hide information from logs or steal data from the user. In order to activate this, the following sequence must occur: * Log4cxx is configured to use HTMLLayout. * Logger name comes from an untrusted string * Logger with compromised name logs a message * User opens the generated HTML log file in their browser, leading to potential XSS Because logger names are generally constant strings, we assess the impact to users as LOW This issue affects Apache Log4cxx: before 1.5.0. Users are recommended to upgrade to version 1.5.0, which fixes the issue.
CVE-2025-54813: Improper Output Neutralization for Logs vulnerability in Apache Log4cxx. When using JSONLayout, not all payload bytes are properly escaped. If an attacker-supplied message contains certain non-printable characters, these will be passed along in the message and written out as part of the JSON message. This may prevent applications that consume these logs from correctly interpreting the information within them. This issue affects Apache Log4cxx: before 1.5.0. Users are recommended to upgrade to version 1.5.0, which fixes the issue.

Created: 2025-08-22 Last update: 2025-08-23 12:00

debian/patches: 1 patch with invalid metadata high

Among the 3 debian patches available in version 1.4.0-1 of the package, we noticed the following issues:

1 patch with invalid metadata that ought to be fixed.

Created: 2024-05-17 Last update: 2025-03-22 21:30

Build log checks report 2 warnings low

Build log checks report 2 warnings

Created: 2015-08-04 Last update: 2022-06-12 18:07

news

[2025-03-24] log4cxx 1.4.0-1 MIGRATED to testing (Debian testing watch)
[2025-03-22] Accepted log4cxx 1.4.0-1 (source) into unstable (Tobias Frost)
[2025-01-09] log4cxx 1.3.1-1 MIGRATED to testing (Debian testing watch)
[2025-01-04] Accepted log4cxx 1.3.1-1 (source) into unstable (Tobias Frost)
[2024-10-24] log4cxx 1.3.0-1 MIGRATED to testing (Debian testing watch)
[2024-10-20] Accepted log4cxx 1.3.0-1 (source) into unstable (Tobias Frost)
[2024-05-19] log4cxx 1.2.0-1 MIGRATED to testing (Debian testing watch)
[2024-05-16] Accepted log4cxx 1.2.0-1 (source) into unstable (Tobias Frost)
[2023-06-29] log4cxx 1.1.0-1 MIGRATED to testing (Debian testing watch)
[2023-06-23] Accepted log4cxx 1.1.0-1 (source) into unstable (Tobias Frost)
[2023-05-09] Accepted log4cxx 1.1.0-1~exp1 (source) into experimental (Tobias Frost)
[2023-01-11] log4cxx 1.0.0-1 MIGRATED to testing (Debian testing watch)
[2023-01-09] Accepted log4cxx 1.0.0-1 (source) into unstable (Tobias Frost)
[2023-01-06] Accepted log4cxx 1.0.0~rc1-1 (source) into experimental (Tobias Frost)
[2023-01-01] Accepted log4cxx 1.0.0~~gitcbd23ff1-1~exp1 (source amd64 all) into experimental (Debian FTP Masters) (signed by: Tobias Frost)
[2022-06-14] log4cxx 0.13.0-2 MIGRATED to testing (Debian testing watch)
[2022-06-12] Accepted log4cxx 0.13.0-2 (source) into unstable (Tobias Frost)
[2022-05-27] Accepted log4cxx 0.13.0-1 (source amd64 all) into experimental, experimental (Debian FTP Masters) (signed by: Tobias Frost)
[2022-01-12] log4cxx 0.12.1-4 MIGRATED to testing (Debian testing watch)
[2022-01-09] Accepted log4cxx 0.12.1-4 (source) into unstable (Tobias Frost)
[2022-01-07] Accepted log4cxx 0.12.1-3 (source) into experimental (Tobias Frost)
[2022-01-07] Accepted log4cxx 0.12.1-2 (source) into experimental (Tobias Frost)
[2021-12-15] Accepted log4cxx 0.12.1-1 (source amd64 all) into experimental, experimental (Debian FTP Masters) (signed by: Tobias Frost)
[2021-12-07] log4cxx 0.11.0-3 MIGRATED to testing (Debian testing watch)
[2021-12-05] Accepted log4cxx 0.11.0-3 (source) into unstable (Tobias Frost)
[2020-09-18] log4cxx 0.11.0-2 MIGRATED to testing (Debian testing watch)
[2020-09-16] Accepted log4cxx 0.11.0-2 (source) into unstable (Tobias Frost)
[2020-09-08] Accepted log4cxx 0.11.0-1 (source amd64 all) into experimental, experimental (Debian FTP Masters) (signed by: Tobias Frost)
[2020-08-29] log4cxx 0.10.0-16 MIGRATED to testing (Debian testing watch)
[2020-08-23] Accepted log4cxx 0.10.0-16 (source) into unstable (Tobias Frost)

1
2

bugs [bug history graph]

all: 2
RC: 0
I&N: 2
M&W: 0
F&P: 0
patch: 0

links

homepage
lintian
buildd: logs, checks, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 1.4.0-1
1 bug

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers

Report problems to the tracker.debian.org pseudo-package in the Debian BTS.

Documentation — Bugs — Git Repository — Contributing