OCPBUGS-105861: block vendor.send_raw step exposure CVE-2026-54423(release-4.21)

[amitesh1201]

Summary

• Removes the @base.deploy_step, @base.clean_step, and @base.service_step decorators from VendorPassthru.send_raw in ipmitool.py, preventing send_raw from being invoked through deploy/clean/service workflows.
• Removes _send_raw_step_args dictionary that is no longer needed.
• Removes two tests (test_send_raw_bytes_is_in_step_list and test_send_raw_bytes_from_clean_step) that assert the now-removed step registration behavior.
• The @base.passthru HTTP API is preserved and continues to enforce its own RBAC.

Background

The upstream fix (openstack/ironic@7bbe5a2) adds vendor.send_raw to the disallow_*_steps config blocklist defaults, but that config infrastructure does not exist on this branch. This alternative fix removes the step registration entirely to achieve the same security outcome.

Tracker

• OCPBUGS-105861
• CVE: CVE-2026-54423
• Advisory: OSSA-2026-025

Made with Cursor

[openshift-ci-robot]

@amitesh1201: This pull request references Jira Issue OCPBUGS-105861, which is invalid:

• expected dependent Jira Issue OCPBUGS-105863 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED 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:

Summary

• Removes the @base.deploy_step, @base.clean_step, and @base.service_step decorators from VendorPassthru.send_raw in ipmitool.py, preventing send_raw from being invoked through deploy/clean/service workflows.
• Removes _send_raw_step_args dictionary that is no longer needed.
• Removes two tests (test_send_raw_bytes_is_in_step_list and test_send_raw_bytes_from_clean_step) that assert the now-removed step registration behavior.
• The @base.passthru HTTP API is preserved and continues to enforce its own RBAC.

Background

The upstream fix (openstack/ironic@7bbe5a2) adds vendor.send_raw to the disallow_*_steps config blocklist defaults, but that config infrastructure does not exist on this branch. This alternative fix removes the step registration entirely to achieve the same security outcome.

Tracker

• OCPBUGS-105861
• CVE: CVE-2026-54423
• Advisory: OSSA-2026-025

Made with Cursor

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]

@amitesh1201: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[elfosardo]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: amitesh1201, elfosardo

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:

• OWNERS [elfosardo]

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

[amitesh1201]

/jira refresh

[openshift-ci-robot]

@amitesh1201: This pull request references Jira Issue OCPBUGS-105861, which is invalid:

• expected dependent Jira Issue OCPBUGS-105863 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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:

/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.

[prdhamdh]

/verified by CI test results

[openshift-ci-robot]

@prdhamdh: This PR has been marked as verified by CI test results.

Details

In response to this:

/verified by CI test results

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.