Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 894478 (CVE-2022-41723, CVE-2022-41724, CVE-2022-41725) - <dev-lang/go-{1.19.6, 1.20.1}: Multiple vulnerabilities
Summary: <dev-lang/go-{1.19.6, 1.20.1}: Multiple vulnerabilities
Alias: CVE-2022-41723, CVE-2022-41724, CVE-2022-41725
Product: Gentoo Security
Classification: Unclassified
Component: Vulnerabilities (show other bugs)
Hardware: All Linux
: Normal minor (vote)
Assignee: Gentoo Security
Whiteboard: B3 [glsa+]
Depends on: 894470 901379
  Show dependency tree
Reported: 2023-02-15 02:04 UTC by Sam James
Modified: 2023-11-25 08:59 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-02-15 02:04:44 UTC


    path/filepath: path traversal in filepath.Clean on Windows

    On Windows, the filepath.Clean function could transform an invalid path such as a/../c:/b into the valid path c:\b. This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack. The filepath.Clean function will now transform this path into the relative (but still invalid) path .\c:\b.

    Thanks to RyotaK ( for reporting this issue.

    This is CVE-2022-41722 and Go issue

    net/http, mime/multipart: denial of service from excessive resource consumption

    Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

    ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files.

    ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous.

    ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct.

    Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.

    Thanks to Ameya Darshan and Jakob Ackermann (@das7pad) for reporting this issue.

    This is CVE-2022-41725 and Go issue

    crypto/tls: large handshake records may cause panics

    Both clients and servers may send large TLS handshake records which cause servers and clients,
    respectively, to panic when attempting to construct responses.

    This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption
    (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request
    client certificates (by setting Config.ClientAuth >= RequestClientCert).

    Thanks to Marten Seemann for reporting this issue.

    This is CVE-2022-41724 and Go issue

    net/http: avoid quadratic complexity in HPACK decoding

    A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.

    This issue is also fixed in v0.7.0, for users manually configuring HTTP/2.

    Thanks to Philippe Antoine (Catena cyber) for reporting this issue.

    This is CVE-2022-41723 and Go issue
Comment 1 Larry the Git Cow gentoo-dev 2023-11-25 08:57:35 UTC
The bug has been referenced in the following commit(s):

commit 7f1e599c82e7f7f6b21bf1127d01d7dfa903e21c
Author:     GLSAMaker <>
AuthorDate: 2023-11-25 08:56:49 +0000
Commit:     Hans de Graaff <>
CommitDate: 2023-11-25 08:57:21 +0000

    [ GLSA 202311-09 ] Go: Multiple Vulnerabilities
    Signed-off-by: GLSAMaker <>
    Signed-off-by: Hans de Graaff <>

 glsa-202311-09.xml | 73 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 73 insertions(+)