Skip to content

OCPBUGS-102453: Use patched x/net fork v0.35.0-sec.4 - #191

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

prabhapa wants to merge 1 commit into
openshift:release-4.13from
prabhapa:cve/4.13/OCPBUGS-102453

Conversation

@prabhapa

Copy link
Copy Markdown

Summary

This PR replaces golang.org/x/net with github.com/openshift-sustaining/net@v0.35.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.13 branch is built with Go 1.19 and cannot consume that upstream release. The v0.35.0-sec.4 sustaining fork carries the compatible backport for this Go version.

Source

Jira coverage

This shared source change addresses:

  • OCPBUGS-102453 — openshift4/ose-prometheus-node-exporter

@openshift-merge-bot

Copy link
Copy Markdown

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. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 24, 2026
@openshift-ci-robot

Copy link
Copy Markdown

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

  • expected dependent Jira Issue OCPBUGS-102636 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.35.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.13 branch is built with Go 1.19 and cannot consume that upstream release. The v0.35.0-sec.4 sustaining fork carries the compatible backport for this Go version.

Source

Jira coverage

This shared source change addresses:

  • OCPBUGS-102453 — openshift4/ose-prometheus-node-exporter

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 commented Sep 24, 2026

Copy link
Copy Markdown

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

@simonpasquier

Copy link
Copy Markdown

/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 25, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 25, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@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 commented Sep 25, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: prabhapa, 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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 25, 2026
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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants