Bug 2068507 - CVE-2022-0778 openssl: Infinite loop in BN_mod_sqrt() reachable when parsing certificates [ovirt-4.5]
Summary: CVE-2022-0778 openssl: Infinite loop in BN_mod_sqrt() reachable when parsing ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-node
Classification: oVirt
Component: Included packages
Version: 4.4.10.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.5.0
: 4.5.0
Assignee: Sandro Bonazzola
QA Contact: Yaning Wang
URL: https://koji.mbox.centos.org/koji/pac...
Whiteboard:
Depends On: 2067145 2067146
Blocks: CVE-2022-0778
TreeView+ depends on / blocked
 
Reported: 2022-03-25 14:31 UTC by Sandro Bonazzola
Modified: 2022-04-20 06:33 UTC (History)
12 users (show)

Fixed In Version: openssl-1.1.1k-6.el8
Doc Type: Release Note
Doc Text:
oVirt Node includes updated openssl packages providing fixes for [CVE-2022-0778](https://bugzilla.redhat.com/show_bug.cgi?id=2062202)
Clone Of:
Environment:
Last Closed: 2022-04-20 06:33:59 UTC
oVirt Team: Node
Embargoed:
sbonazzo: ovirt-4.5+
cshao: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-45455 0 None None None 2022-03-25 14:36:59 UTC

Description Sandro Bonazzola 2022-03-25 14:31:53 UTC 
This bug was created to ensure that one or more security vulnerabilities are fixed in affected versions of oVirt.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
Comment 1 RHEL Program Management 2022-03-25 14:32:10 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 3 Sandro Bonazzola 2022-04-20 06:33:59 UTC 
This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.