<html>
<head>
<base href="https://bugzilla.rosalinux.ru/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Platform</th>
<td>2021.1
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_CONFIRMED "
title="CONFIRMED - [CVE 21] libxml2 2.9.14 CVEs found"
href="https://bugzilla.rosalinux.ru/show_bug.cgi?id=13557">13557</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[CVE 21] libxml2 2.9.14 CVEs found
</td>
</tr>
<tr>
<th>Classification</th>
<td>ROSA-based products
</td>
</tr>
<tr>
<th>Product</th>
<td>ROSA Fresh
</td>
</tr>
<tr>
<th>Version</th>
<td>All
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>URL</th>
<td>CVE-2023-28484, CVE-2023-29469,
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>CONFIRMED
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>Normal
</td>
</tr>
<tr>
<th>Component</th>
<td>System (kernel, glibc, systemd, bash, PAM...)
</td>
</tr>
<tr>
<th>Assignee</th>
<td>bugs@lists.rosalinux.ru
</td>
</tr>
<tr>
<th>Reporter</th>
<td>y.tumanov@rosalinux.ru
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>bugs@lists.rosalinux.ru
</td>
</tr>
<tr>
<th>CC</th>
<td>e.kosachev@rosalinux.ru, s.matveev@rosalinux.ru, y.tumanov@rosalinux.ru
</td>
</tr>
<tr>
<th>Target Milestone</th>
<td>---
</td>
</tr>
<tr>
<th>Flags</th>
<td>secteam_verified?
</td>
</tr></table>
<p>
<div>
<pre>Please patch CVEs for package libxml2 version 2.9.14
INFO (CVEs are): libxml2 2.9.14
cves found
CVE-2023-28484
Desc: In libxml2 before 2.10.4, parsing of certain invalid XSD schemas can lead
to a NULL pointer dereference and subsequently a segfault. This occurs in
xmlSchemaFixupComplexType in xmlschemas.c.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-28484">https://nvd.nist.gov/vuln/detail/CVE-2023-28484</a>
Severity: MEDIUM
CVE-2023-29469
Desc: An issue was discovered in libxml2 before 2.10.4. When hashing empty dict
strings in a crafted XML document, xmlDictComputeFastKey in dict.c can produce
non-deterministic values, leading to various logic and memory errors, such as a
double free. This behavior occurs because there is an attempt to use the first
byte of an empty string, and any value is possible (not solely the '\0' value).
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-29469">https://nvd.nist.gov/vuln/detail/CVE-2023-29469</a>
Severity: MEDIUM</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>