Описание
Security update for go1.20
This update for go1.20 fixes the following issues:
Update to version 1.20.3:
- CVE-2023-24534: security: net/http, net/textproto: denial of service from excessive memory allocation (bsc#1210127)
- CVE-2023-24536: security: net/http, net/textproto, mime/multipart: denial of service from excessive resource consumption (bsc#1210128)
- CVE-2023-24537: security: go/parser: infinite loop in parsing (bsc#1210129)
- CVE-2023-24538: security: html/template: backticks not treated as string delimiters (bsc#1210130)
- x/text: building as a plugin failure on darwin/arm64
- cmd/go: timeout on darwin-amd64-race builder
- internal/testpty: fails on some Linux machines due to incorrect error handling
- cmd/link: Incorrect symbol linked in darwin/arm64
- cmd/link: linker fails on linux/amd64 when gcc's lto options are used
- cmd/link/internal/arm: off-by-one error in trampoline phase call reachability calculation
- time: time zone lookup using extend string makes wrong start time for non-DST zones
- runtime: crash on linux-ppc64le
- cmd/compile: crypto/elliptic build error under -linkshared mode
- cmd/compile: unsafe.SliceData incoherent resuilt with nil argument
Список пакетов
Container bci/golang:latest
SUSE Linux Enterprise Module for Development Tools 15 SP4
openSUSE Leap 15.4
Ссылки
- Link for SUSE-SU-2023:1791-1
- E-Mail link for SUSE-SU-2023:1791-1
- SUSE Security Ratings
- SUSE Bug 1206346
- SUSE Bug 1210127
- SUSE Bug 1210128
- SUSE Bug 1210129
- SUSE Bug 1210130
- SUSE CVE CVE-2023-24534 page
- SUSE CVE CVE-2023-24536 page
- SUSE CVE CVE-2023-24537 page
- SUSE CVE CVE-2023-24538 page
Описание
HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service. Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service. With fix, header parsing now correctly allocates only the memory required to hold parsed headers.
Затронутые продукты
Ссылки
- CVE-2023-24534
- SUSE Bug 1210127
Описание
Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts. This stems from several causes: 1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended. 2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts. 3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector. The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations. In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms: 1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=. 2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.
Затронутые продукты
Ссылки
- CVE-2023-24536
- SUSE Bug 1210128
Описание
Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.
Затронутые продукты
Ссылки
- CVE-2023-24537
- SUSE Bug 1210129
Описание
Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected. Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template. As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml. With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21. Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.
Затронутые продукты
Ссылки
- CVE-2023-24538
- SUSE Bug 1210130