It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2024-477 advisory.

  - A malicious HTTP sender can use chunk extensions to cause a receiver reading from a request or response     body to read many more bytes from the network than are in the body. A malicious HTTP client can further     exploit this to cause a server to automatically read a large amount of data (up to about 1GiB) when a     handler fails to read the entire body of a request. Chunk extensions are a little-used HTTP feature which     permit including additional metadata in a request or response body sent using the chunked encoding. The     net/http chunked encoding reader discards this metadata. A sender can exploit this by inserting a large     metadata segment with each byte transferred. The chunk reader now produces an error if the ratio of real     body to encoded bytes grows too small. (CVE-2023-39326)

  - The filepath package does not recognize paths with a \??\ prefix as special. On Windows, a path beginning     with \??\ is a Root Local Device path equivalent to a path beginning with \\?\. Paths with a \??\ prefix     may be used to access arbitrary locations on the system. For example, the path \??\c:\x is equivalent to     the more common path c:\x. Before fix, Clean could convert a rooted path such as \a\..\??\b into the root     local device path \??\b. Clean will now convert this to .\??\b. Similarly, Join(\, ??, b) could convert a     seemingly innocent sequence of path elements into the root local device path \??\b. Join will now convert     this to \.\??\b. In addition, with fix, IsAbs now correctly reports paths beginning with \??\ as absolute,     and VolumeName correctly reports the \??\ prefix as a volume name. UPDATE: Go 1.20.11 and Go 1.21.4     inadvertently changed the definition of the volume name in Windows paths starting with \?, resulting in     filepath.Clean(\?\c:) returning \?\c: rather than \?\c:\ (among other effects). The previous behavior has     been restored. (CVE-2023-45283)

  - On Windows, The IsLocal function does not correctly detect reserved device names in some cases. Reserved     names followed by spaces, such as COM1 , and reserved names COM and LPT followed by superscript 1,     2, or 3, are incorrectly reported as local. With fix, IsLocal now correctly reports these names as non-     local. (CVE-2023-45284)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Detections

Analytics

Amazon Linux 2023 : golang, golang-bin, golang-misc (ALAS2023-2024-477)

high Nessus Plugin ID 187686

Version 1.1

Version 1.0

Version 1.1 Mar 8, 2024, 6:26 PM IAVM reference Plugin Feed: 202403081826
Version 1.0 Jan 9, 2024, 3:33 AM New Plugin Feed: 202401090333