Skip to content

[release-4.20] OCPBUGS-77794: upgrade lodash and lodash-es to 4.17.23 to address CVE-2025-13465#3546

Open
sunku5494 wants to merge 1 commit intoopenshift-assisted:release-4.20from
sunku5494:fix-CVE-2025-13465-4.20
Open

[release-4.20] OCPBUGS-77794: upgrade lodash and lodash-es to 4.17.23 to address CVE-2025-13465#3546
sunku5494 wants to merge 1 commit intoopenshift-assisted:release-4.20from
sunku5494:fix-CVE-2025-13465-4.20

Conversation

@sunku5494
Copy link
Copy Markdown
Contributor

@sunku5494 sunku5494 commented Apr 7, 2026

Summary by CodeRabbit

Release Notes

  • Chores

    • Updated base container images and dependencies to OpenShift 4.20
    • Pinned lodash dependencies to version 4.17.23 for improved security
    • Expanded CI workflow triggers to include feature/* and release-* branches
  • UI/UX Improvements

    • Updated version references to OpenShift 4.20
    • Improved layout and messaging for disconnected/air-gapped environment installations
    • Changed preview designations from Developer Preview to Technology Preview
    • Refined external platform integration field visibility based on feature flags

…-2025-13465

Signed-off-by: Venkata Charan Sunku <vsunku@redhat.com>
@openshift-ci-robot openshift-ci-robot added the jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. label Apr 7, 2026
@openshift-ci openshift-ci bot requested review from jgyselov and rawagner April 7, 2026 06:08
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 7, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@sunku5494: This pull request references Jira Issue OCPBUGS-77794, which is invalid:

  • expected the vulnerability to target either version "4.22." or "openshift-4.22.", but it targets "4.20.z" instead

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:

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.

@openshift-ci openshift-ci bot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 7, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Apr 7, 2026

Hi @sunku5494. Thanks for your PR.

I'm waiting for a openshift-assisted 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.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 7, 2026

Caution

Review failed

Failed to post review comments

📝 Walkthrough

Walkthrough

This PR updates CI/build infrastructure to OpenShift 4.20, pins lodash dependencies to 4.17.23, implements cached Yarn bootstrap in container builds, expands GitHub Actions workflow branch triggers, replaces DeveloperPreview with TechnologyPreview components throughout the UI, adjusts feature flag logic for single-cluster installation, and updates version references from 4.19 to 4.20.

Changes

Cohort / File(s) Summary
CI/Build Configuration
.ci-operator.yaml, .github/workflows/pull-request.yaml
Added build_root_image config for golang 1.24 and OpenShift 4.20; expanded pull request workflow triggers to include feature/* and release-* branch patterns.
Container Build & Image Updates
apps/assisted-disconnected-ui/Containerfile.ocp
Updated base images to OpenShift 4.20 (Node.js and Go builders); implemented artifacts-cached Yarn bootstrap with remote sources and build args; added vendored Go build flags; replaced full filesystem copy with project-local copy; updated final runtime base image.
Dependency Version Pins
apps/assisted-disconnected-ui/package.json, apps/assisted-ui/package.json, libs/ui-lib/package.json, package.json
Pinned lodash to ^4.17.23 across multiple package.json files and added workspace-level resolutions for lodash/lodash-es.
UI Component Preview Badge Refactoring
libs/ui-lib/lib/ocm/components/clusterWizard/disconnected/BasicStep.tsx, libs/ui-lib/lib/ocm/components/clusterWizard/disconnected/ReviewStep.tsx, libs/ui-lib/lib/ocm/components/clusters/AssistedInstallerHeader.tsx
Replaced DeveloperPreview component with TechnologyPreview; updated OpenShift version references from 4.19 to 4.20.
UI Component Layout & Feature Flag Logic
libs/ui-lib/lib/ocm/components/clusterWizard/ClusterDetailsForm.tsx, libs/ui-lib/lib/ocm/components/clusterWizard/disconnected/BasicStep.tsx, libs/ui-lib/lib/ocm/components/clusterConfiguration/OcmClusterDetailsFormFields.tsx
Switched layout from PatternFly Split to Flex components; wrapped external platform integration field with isSingleClusterFeatureEnabled condition; added translated explanatory text for disconnected installations; removed Switch label.
Feature Flag Support Logic
libs/ui-lib/lib/ocm/components/featureSupportLevels/ReviewClusterFeatureSupportLevels.tsx
Added isSingleClusterFeatureEnabled feature flag consumption; updated getSupportLevelInfo signature to accept and use the flag in isFullySupported and showVersionWarning calculations.
UI Component Props Updates
libs/ui-lib/lib/ocm/components/clusterWizard/disconnected/InstallDisconnectedSwitch.tsx
Removed localized label prop from Switch component.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~22 minutes

Possibly related PRs

Suggested labels

lgtm, approved, ok-to-test, size/M

Suggested reviewers

  • batzionb
  • LiorSoffer
  • rawagner

Poem

🐰 ✨ From four-point-nineteen to four-point-twenty we hop,
DeveloperPreview badges swapped for TechnologyPreview on top,
Yarn caches, Go vendored, lodash pinned just right,
Flex layouts dance where Split once shined bright!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly specifies the main change: upgrading lodash and lodash-es to version 4.17.23 to address a specific CVE, which is reflected throughout the changeset (package.json updates, root resolutions, and related infrastructure updates).
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
⚔️ Resolve merge conflicts
  • Resolve merge conflict in branch fix-CVE-2025-13465-4.20

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 and usage tips.

@openshift-ci openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Apr 7, 2026
@sunku5494 sunku5494 changed the base branch from master to release-4.20 April 7, 2026 06:09
@openshift-ci-robot
Copy link
Copy Markdown

@sunku5494: This pull request references Jira Issue OCPBUGS-77794, which is invalid:

  • expected dependent Jira Issue OCPBUGS-81587 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

Details

In response to this:

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.

@openshift-ci openshift-ci bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Apr 7, 2026
@jgyselov
Copy link
Copy Markdown
Contributor

jgyselov commented Apr 7, 2026

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 7, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 7, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Apr 7, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgyselov, sunku5494

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

The pull request process is described 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 openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Apr 7, 2026
@sunku5494
Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 12, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@sunku5494: This pull request references Jira Issue OCPBUGS-77794, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.z) matches configured target version for branch (4.20.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-81587 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-81587 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0, 4.21.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@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.

@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 15, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Apr 15, 2026

PR needs rebase.

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.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a 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. lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants