<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] rpm 4.17.0 CVEs found"
href="https://bugzilla.rosalinux.ru/show_bug.cgi?id=13307">13307</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[CVE 21] rpm 4.17.0 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-2021-3521, CVE-2021-35937, CVE-2021-35938, CVE-2021-35939,
</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>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 rpm version 4.17.0
INFO (CVEs are): rpm 4.17.0
cves found
CVE-2021-3521
Desc: There is a flaw in RPM's signature functionality. OpenPGP subkeys are
associated with a primary key via a "binding signature." RPM does not check the
binding signature of subkeys prior to importing them. If an attacker is able to
add or socially engineer another party to add a malicious subkey to a
legitimate public key, RPM could wrongly trust a malicious signature. The
greatest impact of this flaw is to data integrity. To exploit this flaw, an
attacker must either compromise an RPM repository or convince an administrator
to install an untrusted RPM or public key. It is strongly recommended to only
use RPMs and public keys from trusted sources.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-3521">https://nvd.nist.gov/vuln/detail/CVE-2021-3521</a>
Severity: MEDIUM
CVE-2021-35937
Desc: A race condition vulnerability was found in rpm. A local unprivileged
user could use this flaw to bypass the checks that were introduced in response
to CVE-2017-7500 and CVE-2017-7501, potentially gaining root privileges. The
highest threat from this vulnerability is to data confidentiality and integrity
as well as system availability.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-35937">https://nvd.nist.gov/vuln/detail/CVE-2021-35937</a>
Severity: MEDIUM
CVE-2021-35938
Desc: A symbolic link issue was found in rpm. It occurs when rpm sets the
desired permissions and credentials after installing a file. A local
unprivileged user could use this flaw to exchange the original file with a
symbolic link to a security-critical file and escalate their privileges on the
system. The highest threat from this vulnerability is to data confidentiality
and integrity as well as system availability.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-35938">https://nvd.nist.gov/vuln/detail/CVE-2021-35938</a>
Severity: MEDIUM
CVE-2021-35939
Desc: It was found that the fix for CVE-2017-7500 and CVE-2017-7501 was
incomplete: the check was only implemented for the parent directory of the file
to be created. A local unprivileged user who owns another ancestor directory
could potentially use this flaw to gain root privileges. The highest threat
from this vulnerability is to data confidentiality and integrity as well as
system availability.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-35939">https://nvd.nist.gov/vuln/detail/CVE-2021-35939</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>