Summary
Package updates are available for Amazon Linux 2023 that fix the following vulnerabilities: CVE-2025-68121: crypto/tls: Config.Clone copies automatically generated session ticket keys, session resumption does not account for the expiration of full certificate chain CVE-2025-61730: crypto/tls: handshake messages may be processed at the incorrect encryption level CVE-2025-61728: archive/zip: denial of service when parsing arbitrary ZIP archives CVE-2025-61726: net/http: memory exhaustion in Request.ParseForm
Fixed packages 7
| Release | Package | Fixed in |
|---|---|---|
| Amazon Linux · 2023 | captree | 0:2.73-1.amzn2023.0.6 |
| Amazon Linux · 2023 | captree-debuginfo | 0:2.73-1.amzn2023.0.6 |
| Amazon Linux · 2023 | libcap | 0:2.73-1.amzn2023.0.6 |
| Amazon Linux · 2023 | libcap-debuginfo | 0:2.73-1.amzn2023.0.6 |
| Amazon Linux · 2023 | libcap-debugsource | 0:2.73-1.amzn2023.0.6 |
| Amazon Linux · 2023 | libcap-devel | 0:2.73-1.amzn2023.0.6 |
| Amazon Linux · 2023 | libcap-static | 0:2.73-1.amzn2023.0.6 |
Vulnerabilities 4
-
Critical 9.1
Unexpected session resumption in crypto/tls
During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user ca…
-
High 7.5
Memory exhaustion in query parameter parsing in net/url
The net/url package does not set a limit on the number of query parameters in a query. While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encode…
-
Medium 6.5
Excessive CPU consumption when building archive index in archive/zip
archive/zip uses a super-linear file name indexing algorithm that is invoked the first time a file in an archive is opened. This can lead to a denial of service when consuming a maliciously constructed ZIP archive.
-
Medium 5.3
Handshake messages may be processed at the incorrect encryption level in crypto/tls
During the TLS 1.3 handshake if multiple messages are sent in records that span encryption level boundaries (for instance the Client Hello and Encrypted Extensions messages), the subsequent messages may be processed before the encryption level changes. This c…