renovate[bot]
commented
5 months ago ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):
- 2 additional dependencies were updated
Details:
| Package | Change |
|---|---|
golang.org/x/sys |
v0.15.0 -> v0.18.0 |
golang.org/x/term |
v0.15.0 -> v0.18.0 |
This PR contains the following updates:
v0.17.0->v0.23.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.
net/http, x/net/http2: close connections when receiving too many headers
BIT-golang-2023-45288 / CVE-2023-45288 / GHSA-4v7x-pqxf-cx7m / GO-2024-2687
More information
#### Details 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. #### Severity - CVSS Score: 5.3 / 10 (Medium) - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L` #### References - [https://nvd.nist.gov/vuln/detail/CVE-2023-45288](https://nvd.nist.gov/vuln/detail/CVE-2023-45288) - [https://go.dev/cl/576155](https://go.dev/cl/576155) - [https://go.dev/issue/65051](https://go.dev/issue/65051) - [https://groups.google.com/g/golang-announce/c/YgW0sx8mN3M](https://groups.google.com/g/golang-announce/c/YgW0sx8mN3M) - [https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QRYFHIQ6XRKRYBI2F5UESH67BJBQXUPT](https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QRYFHIQ6XRKRYBI2F5UESH67BJBQXUPT) - [https://nowotarski.info/http2-continuation-flood-technical-details](https://nowotarski.info/http2-continuation-flood-technical-details) - [https://pkg.go.dev/vuln/GO-2024-2687](https://pkg.go.dev/vuln/GO-2024-2687) - [https://security.netapp.com/advisory/ntap-20240419-0009](https://security.netapp.com/advisory/ntap-20240419-0009) - [http://www.openwall.com/lists/oss-security/2024/04/03/16](http://www.openwall.com/lists/oss-security/2024/04/03/16) - [http://www.openwall.com/lists/oss-security/2024/04/05/4](http://www.openwall.com/lists/oss-security/2024/04/05/4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-4v7x-pqxf-cx7m) and the [GitHub Advisory Database](https://togithub.com/github/advisory-database) ([CC-BY 4.0](https://togithub.com/github/advisory-database/blob/main/LICENSE.md)).HTTP/2 CONTINUATION flood in net/http
BIT-golang-2023-45288 / CVE-2023-45288 / GHSA-4v7x-pqxf-cx7m / GO-2024-2687
More information
#### Details 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. #### Severity Unknown #### References - [https://go.dev/issue/65051](https://go.dev/issue/65051) - [https://go.dev/cl/576155](https://go.dev/cl/576155) - [https://groups.google.com/g/golang-announce/c/YgW0sx8mN3M](https://groups.google.com/g/golang-announce/c/YgW0sx8mN3M) This data is provided by [OSV](https://osv.dev/vulnerability/GO-2024-2687) and the [Go Vulnerability Database](https://togithub.com/golang/vulndb) ([CC-BY 4.0](https://togithub.com/golang/vulndb#license)).Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.