Описание
Security update for log4cxx
This update for log4cxx fixes the following issues:
Changes in log4cxx:
-
update to 1.7.0 (bsc#1261994, CVE-2026-40023):
- Non-ascii characters incorrectly encoded in JSON output [#615]
- XML output could contain characters not allowed by the XML 1.0 specification
- An XML configuration file with recursive references caused program termination [#605]
- Possible undefined behavior during a configuration change
- Message loss when the calculation of a logged value also logs
- ODBCAppender prepared statement value buffers had incorrect lifetimes [#581]
-
update to 1.6.0:
- Configuration ${varname} values can be set programatically prior to loading a configuration file (see com/foo/config4.cpp) [#520]
- The current executable's file name and its components are available for use in a configuration file and the LOG4CXX_CONFIGURATION environment variable (see log4cxx::spi::Configurator::properties). [#520]
- Console output (Log4cxx internal logging and BasicConfigurator) use a color per message level by default [#529]
- New logging macros that defer binary-to-text conversion until used in AsyncAppender's background thread
- A simplified way to attach an AsyncAppender to a logger using a configuration file [#550]
Список пакетов
openSUSE Leap 16.0
Ссылки
- SUSE Security Ratings
- SUSE Bug 1261994
- SUSE CVE CVE-2026-40023 page
Описание
Apache Log4cxx's XMLLayout https://logging.apache.org/log4cxx/1.7.0/classlog4cxx_1_1xml_1_1XMLLayout.html , in versions before 1.7.0, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets in log messages, NDC, and MDC property keys and values, producing invalid XML output. Conforming XML parsers must reject such documents with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records. An attacker who can influence logged data can exploit this to suppress individual log records, impairing audit trails and detection of malicious activity. Users are advised to upgrade to Apache Log4cxx 1.7.0, which fixes this issue.
Затронутые продукты
Ссылки
- CVE-2026-40023
- SUSE Bug 1261994