Re: git: 9a596e5a5345 - main - security/vuxml: Document libxml2 vulnerabilities

From: Daniel Engberg <diizzy_at_FreeBSD.org>
Date: Sat, 31 May 2025 17:38:49 UTC
On 2025-05-31 19:31, Fernando Apesteguía wrote:
> 
> 
> On Sat, May 31, 2025 at 7:18 PM Daniel Engberg <diizzy@freebsd.org 
> <mailto:diizzy@freebsd.org>> wrote:
> 
>     The branch main has been updated by diizzy:
> 
>     URL: https://cgit.FreeBSD.org/ports/commit/?
>     id=9a596e5a5345db82dcf952243faa5e9d80d2ef1b <https://
>     cgit.FreeBSD.org/ports/commit/?
>     id=9a596e5a5345db82dcf952243faa5e9d80d2ef1b>
> 
>     commit 9a596e5a5345db82dcf952243faa5e9d80d2ef1b
>     Author:     Daniel Engberg <diizzy@FreeBSD.org>
>     AuthorDate: 2025-05-31 17:17:46 +0000
>     Commit:     Daniel Engberg <diizzy@FreeBSD.org>
>     CommitDate: 2025-05-31 17:17:49 +0000
> 
>          security/vuxml: Document libxml2 vulnerabilities
> 
>          Document CVE-2024-56171, CVE-2025-24928 and CVE-2025-32414
>     ---
>       security/vuxml/vuln/2025.xml | 89 ++++++++++++++++++++++++++++++++
>     ++++++++++++
>       1 file changed, 89 insertions(+)
> 
>     diff --git a/security/vuxml/vuln/2025.xml b/security/vuxml/vuln/2025.xml
>     index 4681d7869854..1cd062837b12 100644
>     --- a/security/vuxml/vuln/2025.xml
>     +++ b/security/vuxml/vuln/2025.xml
>     @@ -1,3 +1,92 @@
>     +  <vuln vid="2926c487-3e53-11f0-95d4-00a098b42aeb">
>     +    <topic>libxml2 -- Out-of-bounds memory access</topic>
>     +    <affects>
>     +      <package>
>     +       <name>xmlsoft</name>
> 
> 
> ^^^^^^^^^^^^^^^^^^^
> 
> What port is xmlsoft? Shouldn't this be libxml2?

That's the vendor name, no idea why it got picked up while adding last 
entry. I've pushed a fix. Thanks for notifying :)
> 
>     +       <range><lt>2.14.2</lt></range>
>     +      </package>
>     +    </affects>
>     +    <description>
>     +       <body xmlns="http://www.w3.org/1999/xhtml <http://
>     www.w3.org/1999/xhtml>">
>     +       <p>cve@mitre.org <mailto:cve@mitre.org> reports:</p>
>     +       <blockquote cite="https://gitlab.gnome.org/GNOME/libxml2/-/
>     issues/889 <https://gitlab.gnome.org/GNOME/libxml2/-/issues/889>">
>     +         <p>In libxml2 before 2.13.8 and 2.14.x before 2.14.2, out-
>     of-bounds
>     +       memory access can occur in the Python API (Python bindings)
>     because
>     +       of an incorrect return value.  This occurs in
>     xmlPythonFileRead and
>     +       xmlPythonFileReadRaw because of a difference between bytes and
>     +       characters.</p>
>     +       </blockquote>
>     +       </body>
>     +    </description>
>     +    <references>
>     +      <cvename>CVE-2025-32414</cvename>
>     +      <url>https://nvd.nist.gov/vuln/detail/CVE-2025-32414
>     <https://nvd.nist.gov/vuln/detail/CVE-2025-32414></url>
>     +    </references>
>     +    <dates>
>     +      <discovery>2025-04-08</discovery>
>     +      <entry>2025-05-31</entry>
>     +    </dates>
>     +  </vuln>
>     +
>     +  <vuln vid="fdd02be0-3e50-11f0-95d4-00a098b42aeb">
>     +    <topic>libxml2 -- Stack-based Buffer Overflow</topic>
>     +    <affects>
>     +      <package>
>     +       <name>libxml2</name>
>     +       <range><lt>2.13.6</lt></range>
>     +      </package>
>     +    </affects>
>     +    <description>
>     +       <body xmlns="http://www.w3.org/1999/xhtml <http://
>     www.w3.org/1999/xhtml>">
>     +       <p>cve@mitre.org <mailto:cve@mitre.org> reports:</p>
>     +       <blockquote cite="https://gitlab.gnome.org/GNOME/libxml2/-/
>     issues/847 <https://gitlab.gnome.org/GNOME/libxml2/-/issues/847>">
>     +         <p>libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a
>     stack-based
>     +       buffer overflow in xmlSnprintfElements in valid.c.  To
>     exploit this,
>     +       DTD validation must occur for an untrusted document or untrusted
>     +       DTD.  NOTE: this is similar to CVE-2017-9047.</p>
>     +       </blockquote>
>     +       </body>
>     +    </description>
>     +    <references>
>     +      <cvename>CVE-2025-24928</cvename>
>     +      <url>https://nvd.nist.gov/vuln/detail/CVE-2025-24928
>     <https://nvd.nist.gov/vuln/detail/CVE-2025-24928></url>
>     +    </references>
>     +    <dates>
>     +      <discovery>2025-02-18</discovery>
>     +      <entry>2025-05-31</entry>
>     +    </dates>
>     +  </vuln>
>     +
>     +  <vuln vid="bd2af307-3e50-11f0-95d4-00a098b42aeb">
>     +    <topic>libxml2 -- Use After Free</topic>
>     +    <affects>
>     +      <package>
>     +       <name>libxml2</name>
>     +       <range><lt>2.13.6</lt></range>
>     +      </package>
>     +    </affects>
>     +    <description>
>     +       <body xmlns="http://www.w3.org/1999/xhtml <http://
>     www.w3.org/1999/xhtml>">
>     +       <p>cve@mitre.org <mailto:cve@mitre.org> reports:</p>
>     +       <blockquote cite="https://gitlab.gnome.org/GNOME/libxml2/-/
>     issues/828 <https://gitlab.gnome.org/GNOME/libxml2/-/issues/828>">
>     +         <p>libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a
>     use-after-free
>     +       in xmlSchemaIDCFillNodeTables and
>     xmlSchemaBubbleIDCNodeTables in
>     +       xmlschemas.c.  To exploit this, a crafted XML document must be
>     +       validated against an XML schema with certain identity
>     constraints,
>     +       or a crafted XML schema must be used.</p>
>     +       </blockquote>
>     +       </body>
>     +    </description>
>     +    <references>
>     +      <cvename>CVE-2024-56171</cvename>
>     +      <url>https://nvd.nist.gov/vuln/detail/CVE-2024-56171
>     <https://nvd.nist.gov/vuln/detail/CVE-2024-56171></url>
>     +    </references>
>     +    <dates>
>     +      <discovery>2025-02-18</discovery>
>     +      <entry>2025-05-31</entry>
>     +    </dates>
>     +  </vuln>
>     +
>         <vuln vid="25acd603-3dde-11f0-8cb5-a8a1599412c6">
>           <topic>chromium -- multiple security fixes</topic>
>           <affects>
>