From: Paul Barker <paul@pbarker.dev>
To: haiqing.bai@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH] libxml-parser-perl: patch CVE-2006-10003
Date: Thu, 16 Apr 2026 20:11:26 +0100 [thread overview]
Message-ID: <f993a1ea7bc959eec48d2c6b97c9ba77012c0edd.camel@pbarker.dev> (raw)
In-Reply-To: <20260415065104.4102961-1-haiqing.bai@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On Wed, 2026-04-15 at 06:51 +0000, haiqing.bai via
lists.openembedded.org wrote:
> From: Haiqing Bai <haiqing.bai@windriver.com>
>
> XML::Parser versions through 2.47 for Perl has an off-by-one
> heap buffer overflow in st_serial_stack. In the case
> (stackptr == stacksize - 1), the stack will NOT be expanded.
> Then the new value will be written at location (++stackptr),
> which equals stacksize and therefore falls just outside the
> allocated buffer. The bug can be observed when parsing an
> XML file with very deep element nesting.
>
> References:
> https://nvd.nist.gov/vuln/detail/CVE-2006-10003
>
> Signed-off-by: Haiqing Bai <haiqing.bai@windriver.com>
We had some questions about this on the patch review call, given the
CVE was assigned with a year of 2006! I was also a little confused
reading about a fix already being present in XML::Parser v2.45, but that
is for CVE-2006-10002 whereas this is CVE-2006-10003 (one digit higher).
So, all seems to be in order and we should take this patch.
Best regards,
--
Paul Barker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2026-04-16 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 6:51 [oe-core][PATCH] libxml-parser-perl: patch CVE-2006-10003 haiqing.bai
2026-04-16 19:11 ` Paul Barker [this message]
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=f993a1ea7bc959eec48d2c6b97c9ba77012c0edd.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=haiqing.bai@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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