Skip to content

DFBUGS-10564: CVE vulnerable Fixes to release-4.20 - #3144

Open
sowmithri2001 wants to merge 1 commit into
red-hat-storage:release-4.20from
sowmithri2001:CVE-vulnerable-4.20
Open

sowmithri2001 wants to merge 1 commit into
red-hat-storage:release-4.20from
sowmithri2001:CVE-vulnerable-4.20

Conversation

@sowmithri2001

Copy link
Copy Markdown
Contributor

Description

jira link : https://redhat.atlassian.net/browse/DFBUGS-10392
https://redhat.atlassian.net/browse/DFBUGS-10564
https://redhat.atlassian.net/browse/DFBUGS-10585
https://redhat.atlassian.net/browse/DFBUGS-10689
https://redhat.atlassian.net/browse/DFBUGS-10709
https://redhat.atlassian.net/browse/DFBUGS-10730
https://redhat.atlassian.net/browse/DFBUGS-9945
https://redhat.atlassian.net/browse/DFBUGS-10165
https://redhat.atlassian.net/browse/DFBUGS-10267
https://redhat.atlassian.net/browse/DFBUGS-10282
https://redhat.atlassian.net/browse/DFBUGS-10300
https://redhat.atlassian.net/browse/DFBUGS-10322

The following packages were added/updated in the resolutions block of package.json to address CVE vulnerabilities:

Tested locally ocp release-4.21 + odf release-4.20-compatibility

Updated:
fast-uri : 3.1.7
js-yaml: 4.3.2
undici: 6.28.1

Added:
nanoid: 3.3.18

Change Type

Please select all applicable options:

  • Bug Fix

Component / Area Impacted

Please select all applicable options:

  • ODF

Screenshots / Recordings

Recordings / Demo Videos

Screen.Recording.2026-09-21.at.4.00.30.PM.mov

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid jira ticket of any type labels Sep 21, 2026
@openshift-ci

openshift-ci Bot commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sowmithri2001
Once this PR has been reviewed and has the lgtm label, please assign sanjalkatiyar for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting label Sep 21, 2026
@openshift-ci-robot

openshift-ci-robot commented Sep 21, 2026 •

Copy link
Copy Markdown

@sowmithri2001: This pull request references [Jira Issue DFBUGS-10564](https://redhat.atlassian.net/browse/DFBUGS-10564), which is invalid:

  • expected the vulnerability to target the "odf-4.20.19" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Description

jira link : https://redhat.atlassian.net/browse/DFBUGS-10392
https://redhat.atlassian.net/browse/DFBUGS-10564
https://redhat.atlassian.net/browse/DFBUGS-10585
https://redhat.atlassian.net/browse/DFBUGS-10689
https://redhat.atlassian.net/browse/DFBUGS-10709
https://redhat.atlassian.net/browse/DFBUGS-10730
https://redhat.atlassian.net/browse/DFBUGS-9945
https://redhat.atlassian.net/browse/DFBUGS-10165
https://redhat.atlassian.net/browse/DFBUGS-10267
https://redhat.atlassian.net/browse/DFBUGS-10282
https://redhat.atlassian.net/browse/DFBUGS-10300
https://redhat.atlassian.net/browse/DFBUGS-10322

The following packages were added/updated in the resolutions block of package.json to address CVE vulnerabilities:

Tested locally ocp release-4.21 + odf release-4.20-compatibility

Updated:
fast-uri : 3.1.7
js-yaml: 4.3.2
undici: 6.28.1

Added:
nanoid: 3.3.18

Change Type

Please select all applicable options:

  • Bug Fix

Component / Area Impacted

Please select all applicable options:

  • ODF

Screenshots / Recordings

Recordings / Demo Videos

Screen.Recording.2026-09-21.at.4.00.30.PM.mov

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@coderabbitai

coderabbitai Bot commented Sep 21, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 82a69b6c-e7b3-4b9e-b6d7-caf0c20d59dc

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@openshift-ci

openshift-ci Bot commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

Hi @sowmithri2001. Thanks for your PR.

I'm waiting for a red-hat-storage member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@Soundarya189r

Copy link
Copy Markdown

/ok-to-test

@Soundarya189r

Copy link
Copy Markdown

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting and removed jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels Oct 5, 2026
@openshift-ci-robot

openshift-ci-robot commented Oct 5, 2026 •

Copy link
Copy Markdown

@Soundarya189r: This pull request references [Jira Issue DFBUGS-10564](https://redhat.atlassian.net/browse/DFBUGS-10564), which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.20.20) matches configured target version for branch (odf-4.20.20)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (sdurgbun@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting jira/valid-reference Indicates that this PR references a valid jira ticket of any type ok-to-test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants