Skip to content

OCPBUGS-103737: Use patched x/net fork v0.43.0-sec.4 - #620

Open
prabhapa wants to merge 1 commit into
openshift:release-4.19from
prabhapa:cve/4.19/OCPBUGS-103737
Open

prabhapa wants to merge 1 commit into
openshift:release-4.19from
prabhapa:cve/4.19/OCPBUGS-103737

Conversation

@prabhapa

Copy link
Copy Markdown

Summary

This PR replaces golang.org/x/net with github.com/openshift-sustaining/net@v0.43.0-sec.4.

Rationale

CVE-2026-33814, a Go HTTP/2 denial of service caused by a malformed SETTINGS_MAX_FRAME_SIZE frame, is fixed upstream in golang.org/x/net v0.53.0, which requires Go 1.25. The release-4.19 branch is built with Go 1.23 and cannot consume that upstream release. The v0.43.0-sec.4 sustaining fork carries the compatible backport for this Go version.

Source

Jira coverage

This shared source change addresses:

  • OCPBUGS-103737 — openshift4/ose-telemeter-rhel9

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@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 24, 2026
@coderabbitai

coderabbitai Bot commented Sep 24, 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: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: b39a7e7f-26ee-489a-8c66-2d232b9b2eb4

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

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

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

Copy link
Copy Markdown
Contributor

@prabhapa: This pull request references Jira Issue OCPBUGS-103737, which is invalid:

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

This PR replaces golang.org/x/net with github.com/openshift-sustaining/net@v0.43.0-sec.4.

Rationale

CVE-2026-33814, a Go HTTP/2 denial of service caused by a malformed SETTINGS_MAX_FRAME_SIZE frame, is fixed upstream in golang.org/x/net v0.53.0, which requires Go 1.25. The release-4.19 branch is built with Go 1.23 and cannot consume that upstream release. The v0.43.0-sec.4 sustaining fork carries the compatible backport for this Go version.

Source

Jira coverage

This shared source change addresses:

  • OCPBUGS-103737 — openshift4/ose-telemeter-rhel9

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 requested review from raptorsun and rexagod September 24, 2026 06:53
@simonpasquier

Copy link
Copy Markdown
Contributor

/approve
/label backport-risk-assessed
/verified by @simonpasquier

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 24, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 24, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@simonpasquier: This PR has been marked as verified by @simonpasquier.

Details

In response to this:

/approve
/label backport-risk-assessed
/verified by @simonpasquier

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 24, 2026
@prabhapa

Copy link
Copy Markdown
Author

/test benchmark\n/test images\n/test integration\n

@prabhapa

Copy link
Copy Markdown
Author

/test benchmark

@prabhapa

Copy link
Copy Markdown
Author

/test images

@prabhapa

Copy link
Copy Markdown
Author

/test integration

@simonpasquier

Copy link
Copy Markdown
Contributor

/override-sticky ci/prow/integration

the integration job isn't relevant for z-stream branches.

@openshift-ci

openshift-ci Bot commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

@simonpasquier: Overrode contexts on behalf of simonpasquier: ci/prow/integration

These overrides will persist across retests on the current HEAD SHA. Pushing a new commit will clear them. Use /override-cancel to remove them.

Details

In response to this:

/override-sticky ci/prow/integration

the integration job isn't relevant for z-stream branches.

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.

@simonpasquier

Copy link
Copy Markdown
Contributor

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@simonpasquier: This pull request references Jira Issue OCPBUGS-103737, which is invalid:

  • expected dependent Jira Issue OCPBUGS-103956 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:

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

@rhdmalone

Copy link
Copy Markdown

/pipeline required

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-aws-ovn
/test e2e-aws-upgrade

@simonpasquier

Copy link
Copy Markdown
Contributor

/jira refresh
/lgtm

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@simonpasquier: This pull request references Jira Issue OCPBUGS-103737, which is invalid:

  • expected dependent Jira Issue OCPBUGS-103956 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:

/jira refresh
/lgtm

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 lgtm Indicates that a PR is ready to be merged. label Nov 2, 2026
@openshift-ci

openshift-ci Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: simonpasquier

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

@rhdmalone

Copy link
Copy Markdown

/test e2e-aws-ovn

@rhdmalone

Copy link
Copy Markdown

/test e2e-aws-ovn

@openshift-ci

openshift-ci Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

@prabhapa: 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.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. 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. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants