From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Titouan Christophe <titouan.christophe@mind.be>
Cc: buildroot@buildroot.org, Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH] package/log4cxx: security bump to v1.7.0
Date: Wed, 22 Apr 2026 18:50:08 +0200 [thread overview]
Message-ID: <1c53d27fa9a08d23111c87bb1b28097c@free.fr> (raw)
In-Reply-To: <20260422135456.3109434-1-titouan.christophe@mind.be>
On 22/04/2026 15:54, Titouan Christophe via buildroot wrote:
> This fixes the following vulnerability:
> - CVE-2026-40023:
> Apache Log4cxx's XMLLayout
> https://logging.apache.org/log4cxx/1.7.0/c
> lasslog4cxx_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.
> https://www.cve.org/CVERecord?id=CVE-2026-40023
>
> Signed-off-by: Titouan Christophe <titouan.christophe@mind.be>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-04-22 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 13:54 [Buildroot] [PATCH] package/log4cxx: security bump to v1.7.0 Titouan Christophe via buildroot
2026-04-22 16:50 ` Julien Olivain via buildroot [this message]
2026-05-04 14:47 ` Thomas Perale via buildroot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1c53d27fa9a08d23111c87bb1b28097c@free.fr \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=titouan.christophe@mind.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox