Bug 2190144

Summary: Include at ODF 4.9 “Multi-Cloud Object Gateway Core” container image the RHEL8 CVE fix on "nodejs:14"
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Rejy M Cyriac <rcyriac>
Component: distributionAssignee: Mudit Agarwal <muagarwa>
Status: CLOSED WONTFIX QA Contact: Joy John Pinto <jopinto>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.9CC: dkhandel, kramdoss, ocs-bugs, odf-bz-bot
Target Milestone: ---Keywords: ZStream
Target Release: ODF 4.9.16   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-27 06:54:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Rejy M Cyriac 2023-04-27 09:40:33 UTC 
RHEL 8 has shipped on 12 April 2023 "nodejs:14" security update RHSA with fix for "Important" CVE


= RHSA-2023:1743 - Security Advisory
  == https://access.redhat.com/errata/RHSA-2023:1743


= CVE
  == https://access.redhat.com/security/cve/CVE-2022-38900


= RPM Errata
  == https://errata.devel.redhat.com/advisory/112285


= Updated build with CVE fix
  ==  nodejs-14-8070020230306170042.bd1311ed


ODF 4.9 “Multi-Cloud Object Gateway Core” Container image is impacted by the CVE, and needs re-spin to include the updated packages.

Being "Important" CVE, the number of days to ship the Container image with fixes is 30 days after fixes have been shipped at RHEL. So the mandatory due date to ship the ODF 4.9 Container image with updated packages is 12 May 2023, to prevent CHI scores (Health Score) from dropping to grade C.
Comment 6 Joy John Pinto 2023-05-23 16:35:04 UTC 
Verified with OCP 4.9.0-0.nightly-2023-04-22-063547 and odf-operator.v4.9.16

sh-4.4$ rpm -q nodejs npm
nodejs-14.21.3-1.module+el8.7.0+18531+81d21ca6.x86_64
npm-6.14.18-1.14.21.3.1.module+el8.7.0+18531+81d21ca6.x86_64

The respective nodejs rpm matches with nodejs-14-8070020230306170042.bd1311ed, hence closing the bug