Summary
The golang packages provide the Go programming language compiler.
Security Fix(es):
* net/http: Denial of service due to improper 100-continue handling in net/http (CVE-2024-24791)
* go/parser: golang: Calling any of the Parse functions containing deeply nested literals can cause a panic/stack exhaustion (CVE-2024-34155)
* encoding/gob: golang: Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion (CVE-2024-34156)
* go/build/constraint: golang: Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion (CVE-2024-34158)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Fixed packages 7
| Release | Package | Fixed in |
|---|---|---|
| AlmaLinux · 9 | go-toolset | 1.21.13-3.el9_4 |
| AlmaLinux · 9 | golang | 1.21.13-3.el9_4 |
| AlmaLinux · 9 | golang-bin | 1.21.13-3.el9_4 |
| AlmaLinux · 9 | golang-docs | 1.21.13-3.el9_4 |
| AlmaLinux · 9 | golang-misc | 1.21.13-3.el9_4 |
| AlmaLinux · 9 | golang-src | 1.21.13-3.el9_4 |
| AlmaLinux · 9 | golang-tests | 1.21.13-3.el9_4 |
Vulnerabilities 4
-
High 7.5
Denial of service due to improper 100-continue handling in net/http
The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next r…
-
High 7.5
Stack exhaustion in Decoder.Decode in encoding/gob
Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.
-
High 7.5
Stack exhaustion in Parse in go/build/constraint
Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.
-
Medium 4.3
Stack exhaustion in all Parse functions in go/parser
Calling any of the Parse functions on Go source code which contains deeply nested literals can cause a panic due to stack exhaustion.
References
-
report
https://access.redhat.com/security/cve/CVE-2024-24791
-
report
https://access.redhat.com/security/cve/CVE-2024-34155
-
report
https://access.redhat.com/security/cve/CVE-2024-34156
-
report
https://access.redhat.com/security/cve/CVE-2024-34158
-
report
https://bugzilla.redhat.com/2295310
-
report
https://bugzilla.redhat.com/2310527
-
report
https://bugzilla.redhat.com/2310528
-
report
https://bugzilla.redhat.com/2310529
-
advisory
https://errata.almalinux.org/9/ALSA-2024-6913.html