opentelemetry-collector-0.144.0-1.el9_7
エラータID: AXSA:2026-330:02
Collector with the supported components for a Cybertrust Japan Co., Ltd. build of OpenTelemetry
Security Fix(es):
* golang: net/url: Memory exhaustion in query parameter parsing in net/url (CVE-2025-61726)
* crypto/tls: Unexpected session resumption in crypto/tls (CVE-2025-68121)
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.
CVE-2025-61726
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-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.
CVE-2025-68121
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 calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.
Update packages.
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-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.
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 calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.
N/A
SRPMS
- opentelemetry-collector-0.144.0-1.el9_7.src.rpm
MD5: f73ac1dd5323f9fde98992a50b6ec221
SHA-256: 007e3f00d565eaaade0996ba770cb161f09f6bc1074ac0fbb53f4187a4cac374
Size: 24.38 MB
Asianux Server 9 for x86_64
- opentelemetry-collector-0.144.0-1.el9_7.x86_64.rpm
MD5: b699424a75dd8a23b648233800b22ccf
SHA-256: 287eb10f1d0fe0c272f54a37e2710f3dfe56879a147b28712b433e826c066d31
Size: 34.50 MB