CVE-2021-20295
Last modified
CVE-2021-20295 is a medium-severity vulnerability rated 6.5/10 on the CVSS scale. It was discovered that the update for the virt:rhel module in the RHSA-2020:4676 (https://access.redhat.com/errata/RHSA-2020:4676) erratum released as part of Red Hat Enterprise Linux 8.3 failed to include the fix for the qemu-kvm component issue CVE-2020-10756, which was previously corrected in virt:rhel/qemu-kvm via erratum RHSA-2020:4059 (https://access.redhat.com/errata/RHSA-2020:4059). CVE-2021-20295 was assigned to that Red Hat specific security regression. EPSS estimates a 0.28% chance of exploitation in the next 30 days.
Description
It was discovered that the update for the virt:rhel module in the RHSA-2020:4676 (https://access.redhat.com/errata/RHSA-2020:4676) erratum released as part of Red Hat Enterprise Linux 8.3 failed to include the fix for the qemu-kvm component issue CVE-2020-10756, which was previously corrected in virt:rhel/qemu-kvm via erratum RHSA-2020:4059 (https://access.redhat.com/errata/RHSA-2020:4059). CVE-2021-20295 was assigned to that Red Hat specific security regression. For more details about the original security issue CVE-2020-10756, refer to bug 1835986 or the CVE page: https://access.redhat.com/security/cve/CVE-2020-10756.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Qemu | Qemu | < 4.2.0-34 |
References
- https://access.redhat.com/security/cve/CVE-2020-10756Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1944075Issue Tracking, Vendor Advisory
- https://security.netapp.com/advisory/ntap-20220519-0003/Third Party Advisory
- https://access.redhat.com/security/cve/CVE-2020-10756Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1944075Issue Tracking, Vendor Advisory
- https://security.netapp.com/advisory/ntap-20220519-0003/Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2021-20295?
How severe is CVE-2021-20295?
How do I fix CVE-2021-20295?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2021
- CVE-2021-2029Vulnerability in the Oracle Scripting product of Oracle E-Bu…9.8
- CVE-2021-20290An improper authorization handling flaw was found in Foreman…6.1
- CVE-2021-20291A deadlock vulnerability was found in 'github.com/containers…6.5
- CVE-2021-20292There is a flaw reported in the Linux kernel in versions bef…6.7
- CVE-2021-20293A reflected Cross-Site Scripting (XSS) flaw was found in RES…6.1
- CVE-2021-20294A flaw was found in binutils readelf 2.35 program. An attack…7.8
- CVE-2021-20296A flaw was found in OpenEXR in versions before 3.0.0-beta. A…5.3
- CVE-2021-20297A flaw was found in NetworkManager in versions before 1.30.0…5.5
- CVE-2021-20298A flaw was found in OpenEXR's B44Compressor. This flaw allow…7.5
- CVE-2021-20299A flaw was found in OpenEXR's Multipart input file functiona…7.5
- CVE-2021-2030Vulnerability in the MySQL Server product of Oracle MySQL (c…4.9
- CVE-2021-20300A flaw was found in OpenEXR's hufUncompress functionality in…5.5
Are you affected by CVE-2021-20295?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
