-
Notifications
You must be signed in to change notification settings - Fork 139
chore(deps): update module golang.org/x/net to v0.36.0 [security] - autoclosed #521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
414340c to
c27a8ad
Compare
|
Ephemeral COPR build failed. @containers/packit-build please check. |
|
/approve |
|
/retest |
c27a8ad to
9da4a8b
Compare
9da4a8b to
ffc0307
Compare
|
/approve |
ffc0307 to
ee06f18
Compare
ee06f18 to
d00e763
Compare
d00e763 to
f457a90
Compare
b0532ee to
84e7a40
Compare
84e7a40 to
b89af5a
Compare
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
|
/approve |
b89af5a to
5d641a8
Compare
5d641a8 to
cb67bf3
Compare
46f2bfb to
c9d2a2b
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
c9d2a2b to
ca57bb1
Compare
|
This PR contains the following updates:
v0.19.0->v0.36.0GitHub Vulnerability Alerts
CVE-2023-45288
An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed. This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send. The fix sets a limit on the amount of excess header frames we will process before closing a connection.
CVE-2025-22870
Matching of hosts against proxy patterns can improperly treat an IPv6 zone ID as a hostname component. For example, when the NO_PROXY environment variable is set to "*.example.com", a request to "[::1%25.example.com]:80` will incorrectly match and not be proxied.
Configuration
📅 Schedule: Branch creation - "" in timezone UTC, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.