USN-7109-1: Go vulnerabilities

Published Nov 14, 2024
·
Updated

Philippe Antoine discovered that Go incorrectly handled crafted HTTP/2 streams. An attacker could possibly use this issue to cause a denial of service. (CVE-2022-41723) Marten Seemann discovered that Go did not properly manage memory under certain circumstances. An attacker could possibly use this issue to cause a panic resulting in a denial of service. (CVE-2022-41724) Ameya Darshan and Jakob Ackermann discovered that Go did not properly validate the amount of memory and disk files ReadForm can consume. An attacker could possibly use this issue to cause a panic resulting in a denial of service. (CVE-2022-41725) Hunter Wittenborn discovered that Go incorrectly handled the sanitization of environment variables. An attacker could possibly use this issue to run arbitrary commands. (CVE-2023-24531) Jakob Ackermann discovered that Go incorrectly handled multipart forms. An attacker could possibly use this issue to consume an excessive amount of resources, resulting in a denial of service. (CVE-2023-24536) Juho Nurminen discovered that Go incorrectly handled certain special characters in directory or file paths. An attacker could possibly use this issue to inject code into the resulting binaries. (CVE-2023-29402) Vincent Dehors discovered that Go incorrectly handled permission bits. An attacker could possibly use this issue to read or write files with elevated privileges. (CVE-2023-29403) Juho Nurminen discovered that Go incorrectly handled certain compiler directives. An attacker could possibly use this issue to execute arbitrary code. (CVE-2023-29404) Juho Nurminen discovered that Go incorrectly handled certain crafted arguments. An attacker could possibly use this issue to execute arbitrary code at build time. (CVE-2023-29405) Bartek Nowotarski discovered that Go incorrectly validated the contents of host headers. A remote attacker could possibly use this issue to inject additional headers or entire requests. (CVE-2023-29406) Takeshi Kaneko discovered that Go did not properly handle comments and special tags in the script context of html/template module. An attacker could possibly use this issue to inject Javascript code and perform a cross-site scripting attack. (CVE-2023-39318, CVE-2023-39319) It was discovered that Go did not properly validate the "//go:cgo" directives during compilation. An attacker could possibly use this issue to inject arbitrary code during compile time. (CVE-2023-39323) It was discovered that Go did not limit the number of simultaneously executing handler goroutines in the net/http module. An attacker could possibly use this issue to cause a panic resulting in a denial of service. (CVE-2023-39325) Bartek Nowotarski was discovered that the Go net/http module did not properly handle the requests when request's headers exceed MaxHeaderBytes. An attacker could possibly use this issue to cause a panic resulting into a denial of service. (CVE-2023-45288) Bartek Nowotarski discovered that the Go net/http module did not properly validate the total size of the parsed form when parsing a multipart form. An attacker could possibly use this issue to cause a panic resulting into a denial of service. (CVE-2023-45290) John Howard discovered that the Go crypto/x509 module did not properly handle a certificate chain which contains a certificate with an unknown public key algorithm. An attacker could possibly use this issue to cause a panic resulting into a denial of service. (CVE-2024-24783) Juho Nurminen discovered that the Go net/mail module did not properly handle comments within display names in the ParseAddressList function. An attacker could possibly use this issue to cause a panic resulting into a denial of service. (CVE-2024-24784) It was discovered that the Go html/template module did not validate errors returned from MarshalJSON methods. An attacker could possibly use this issue to inject arbitrary code into the Go template. (CVE-2024-24785) Yufan You discovered that the Go archive/zip module did not properly handle certain types of invalid zip files differs from the behavior of most zip implementations. An attacker could possibly use this issue to cause a panic resulting into a denial of service. (CVE-2024-24789) Enze Wang and Jianjun Chen discovered that the Go net/netip module did not work as expected for IPv4-mapped IPv6 addresses in various Is methods. An attacker could possibly use this issue to cause a panic resulting into a denial of service. (CVE-2024-24790) Geoff Franks discovered that the Go net/http module did not properly handle responses to requests with an "Expect: 100-continue" header under certain circumstances. An attacker could possibly use this issue to cause a denial of service. (CVE-2024-24791) It was discovered that the Go parser module did not properly handle deeply nested literal values. An attacker could possibly use this issue to cause a panic resulting in a denial of service. (CVE-2024-34155) Md Sakib Anwar discovered that the Go encoding/gob module did not properly handle message decoding under certain circumstances. An attacker could possibly use this issue to cause a panic resulting in a denial of service. (CVE-2024-34156) It was discovered that the Go build module did not properly handle certain build tag lines with deeply nested expressions. An attacker could possibly use this issue to cause a panic resulting in a denial of service. (CVE-2024-34158)

Affected Software

24 affected componentsFixes available
All of the following
ubuntu/golang-1.18<1.18.1-1ubuntu1.2
1.18.1-1ubuntu1.2
Ubuntu Ubuntu=22.04
All of the following
ubuntu/golang-1.18-go<1.18.1-1ubuntu1.2
1.18.1-1ubuntu1.2
Ubuntu Ubuntu=22.04
All of the following
ubuntu/golang-1.18-src<1.18.1-1ubuntu1.2
1.18.1-1ubuntu1.2
Ubuntu Ubuntu=22.04
All of the following
ubuntu/golang-1.18<1.18.1-1ubuntu1~20.04.3
1.18.1-1ubuntu1~20.04.3
Ubuntu Ubuntu=20.04
All of the following
ubuntu/golang-1.18-go<1.18.1-1ubuntu1~20.04.3
1.18.1-1ubuntu1~20.04.3
Ubuntu Ubuntu=20.04
All of the following
ubuntu/golang-1.18-src<1.18.1-1ubuntu1~20.04.3
1.18.1-1ubuntu1~20.04.3
Ubuntu Ubuntu=20.04
All of the following
ubuntu/golang-1.18<1.18.1-1ubuntu1~18.04.4+esm1
1.18.1-1ubuntu1~18.04.4+esm1
Ubuntu Ubuntu=18.04
All of the following
ubuntu/golang-1.18-go<1.18.1-1ubuntu1~18.04.4+esm1
1.18.1-1ubuntu1~18.04.4+esm1
Ubuntu Ubuntu=18.04
All of the following
ubuntu/golang-1.18-src<1.18.1-1ubuntu1~18.04.4+esm1
1.18.1-1ubuntu1~18.04.4+esm1
Ubuntu Ubuntu=18.04
All of the following
ubuntu/golang-1.18<1.18.1-1ubuntu1~16.04.6+esm1
1.18.1-1ubuntu1~16.04.6+esm1
Ubuntu Ubuntu=16.04
All of the following
ubuntu/golang-1.18-go<1.18.1-1ubuntu1~16.04.6+esm1
1.18.1-1ubuntu1~16.04.6+esm1
Ubuntu Ubuntu=16.04
All of the following
ubuntu/golang-1.18-src<1.18.1-1ubuntu1~16.04.6+esm1
1.18.1-1ubuntu1~16.04.6+esm1
Ubuntu Ubuntu=16.04

Event History

Nov 14, 2024
Advisory Published
via Ubuntu·12:00 AM

Frequently Asked Questions

1

What is the severity of USN-7109-1?

The severity of USN-7109-1 is classified as a potential denial of service due to improper handling of crafted HTTP/2 streams.

2

How do I fix USN-7109-1?

To fix USN-7109-1, upgrade to the corrected versions of the affected packages, as detailed in the advisory.

3

Which versions of Go are affected by USN-7109-1?

USN-7109-1 affects Go versions prior to 1.18.1-1ubuntu1.2 on supported Ubuntu releases.

4

What type of vulnerability is associated with USN-7109-1?

USN-7109-1 is associated with a denial of service vulnerability due to improper memory management in Go.

5

Are there any known exploits for USN-7109-1?

There are currently no publicly known exploits for the vulnerability described in USN-7109-1.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203