Path to this page:
./
lang/go122,
The Go programming language
Branch: CURRENT,
Version: 1.22.8,
Package name: go122-1.22.8,
Maintainer: bsiegertThe Go programming language is an open source project to make
programmers more productive.
Go is expressive, concise, clean, and efficient. Its concurrency
mechanisms make it easy to write programs that get the most out of
multicore and networked machines, while its novel type system enables
flexible and modular program construction. Go compiles quickly to
machine code yet has the convenience of garbage collection and the power
of run-time reflection. It's a fast, statically typed, compiled language
that feels like a dynamically typed, interpreted language.
Master sites:
Filesize: 26917.043 KB
Version history: (Expand)
- (2024-10-03) Updated to version: go122-1.22.8
- (2024-09-06) Updated to version: go122-1.22.7
- (2024-08-11) Updated to version: go122-1.22.6
- (2024-07-03) Updated to version: go122-1.22.5
- (2024-06-13) Updated to version: go122-1.22.4
- (2024-05-07) Updated to version: go122-1.22.3
CVS history: (Expand)
2024-04-09 18:57:46 by Jonathan Perkin | Files touched by this commit (2) |
Log message:
go122: Support O_DIRECT on illumos.
|
2024-04-05 20:51:52 by Benny Siegert | Files touched by this commit (3) |
Log message:
This minor release includes 1 security fix following the security policy:
http2: close connections when receiving too many headers
Maintaining HPACK state requires that we parse and process all HEADERS and
CONTINUATION frames on a connection. When a request's headers exceed
MaxHeaderBytes, we don't allocate memory to store the excess headers but we do
parse them. 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.
Set a limit on the amount of excess header frames we will process before
closing a connection.
Thanks to Bartek Nowotarski (https://nowotarski.info/) for reporting this
issue.
This is CVE-2023-45288 and Go issue https://go.dev/issue/65051.
|
2024-04-02 16:12:58 by Jonathan Perkin | Files touched by this commit (2) |
Log message:
go122: Implement syscall.Mkfifo() on illumos.
|
2024-03-05 20:37:52 by Benny Siegert | Files touched by this commit (3) | |
Log message:
go122: update to 1.22.1 (security)
This minor release includes 5 security fixes following the security policy:
- crypto/x509: Verify panics on certificates with an unknown public key
algorithm
Verifying a certificate chain which contains a certificate with an unknown
public key algorithm will cause Certificate.Verify to panic.
This affects all crypto/tls clients, and servers that set Config.ClientAuth
to VerifyClientCertIfGiven or RequireAndVerifyClientCert. The default
behavior is for TLS servers to not verify client certificates.
Thanks to John Howard (Google) for reporting this issue.
This is CVE-2024-24783 and Go issue https://go.dev/issue/65390.
- net/http: memory exhaustion in Request.ParseMultipartForm
When parsing a multipart form (either explicitly with
Request.ParseMultipartForm or implicitly with Request.FormValue,
Request.PostFormValue, or Request.FormFile), limits on the total size of the
parsed form were not applied to the memory consumed while reading a single
form line. This permitted a maliciously crafted input containing very long
lines to cause allocation of arbitrarily large amounts of memory, potentially
leading to memory exhaustion.
ParseMultipartForm now correctly limits the maximum size of form lines.
Thanks to Bartek Nowotarski for reporting this issue.
This is CVE-2023-45290 and Go issue https://go.dev/issue/65383.
- net/http, net/http/cookiejar: incorrect forwarding of sensitive headers and
cookies on HTTP redirect
When following an HTTP redirect to a domain which is not a subdomain match or
exact match of the initial domain, an http.Client does not forward sensitive
headers such as "Authorization" or "Cookie". For example, \
a redirect from
foo.com to www.foo.com will forward the Authorization header, but a redirect
to bar.com will not.
A maliciously crafted HTTP redirect could cause sensitive headers to be
unexpectedly forwarded.
Thanks to Juho Nurminen of Mattermost for reporting this issue.
This is CVE-2023-45289 and Go issue https://go.dev/issue/65065.
- html/template: errors returned from MarshalJSON methods may break template
escaping
If errors returned from MarshalJSON methods contain user controlled data,
they may be used to break the contextual auto-escaping behavior of the
html/template package, allowing for subsequent actions to inject unexpected
content into templates.
Thanks to RyotaK (https://ryotak.net) for reporting this issue.
This is CVE-2024-24785 and Go issue https://go.dev/issue/65697.
- net/mail: comments in display names are incorrectly handled
The ParseAddressList function incorrectly handles comments (text within
parentheses) within display names. Since this is a misalignment with
conforming address parsers, it can result in different trust decisions being
made by programs using different parsers.
Thanks to Juho Nurminen of Mattermost and Slonser
(https://github.com/Slonser) for reporting this issue.
This is CVE-2024-24784 and Go issue https://go.dev/issue/65083.
|