CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2023-45287 – Before Go 1.20, the RSA based key exchange methods in crypto/tls may exhibit a timing side channel
https://notcve.org/view.php?id=CVE-2023-45287
Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits. In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels. Antes de Go 1.20, los intercambios de claves TLS basados en RSA utilizaban la librería math/big, que no es un tiempo constante. • https://go.dev/cl/326012/26 https://go.dev/issue/20654 https://groups.google.com/g/golang-announce/c/QMK8IQALDvA https://people.redhat.com/~hkario/marvin https://pkg.go.dev/vuln/GO-2023-2375 https://security.netapp.com/advisory/ntap-20240112-0005 https://access.redhat.com/security/cve/CVE-2023-45287 https://bugzilla.redhat.com/show_bug.cgi?id=2253193 • CWE-203: Observable Discrepancy CWE-208: Observable Timing Discrepancy •
CVSS: 5.3EPSS: 0%CPEs: 3EXPL: 0CVE-2023-45284 – Incorrect detection of reserved device names on Windows in path/filepath
https://notcve.org/view.php?id=CVE-2023-45284
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. En Windows, la función IsLocal no detecta correctamente los nombres de dispositivos reservados en algunos casos. Los nombres reservados seguidos de espacios, como "COM1", y los nombres reservados "COM" y "LPT" seguidos del superíndice 1, 2 o 3 se informan incorrectamente como locales. • https://go.dev/cl/540277 https://go.dev/issue/63713 https://groups.google.com/g/golang-announce/c/4tU8LZfBFkY https://pkg.go.dev/vuln/GO-2023-2186 •
CVSS: 7.5EPSS: 0%CPEs: 3EXPL: 0CVE-2023-45283 – Insecure parsing of Windows paths with a \??\ prefix in path/filepath
https://notcve.org/view.php?id=CVE-2023-45283
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 \\?\. • http://www.openwall.com/lists/oss-security/2023/12/05/2 https://go.dev/cl/540277 https://go.dev/cl/541175 https://go.dev/issue/63713 https://go.dev/issue/64028 https://groups.google.com/g/golang-announce/c/4tU8LZfBFkY https://groups.google.com/g/golang-dev/c/6ypN5EjibjM/m/KmLVYH_uAgAJ https://pkg.go.dev/vuln/GO-2023-2185 https://security.netapp.com/advisory/ntap-20231214-0008 • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') •
CVSS: 7.5EPSS: 0%CPEs: 2EXPL: 0CVE-2023-46324
https://notcve.org/view.php?id=CVE-2023-46324
pkg/suci/suci.go in free5GC udm before 1.2.0, when Go before 1.19 is used, allows an Invalid Curve Attack because it may compute a shared secret via an uncompressed public key that has not been validated. An attacker can send arbitrary SUCIs to the UDM, which tries to decrypt them via both its private key and the attacker's public key. pkg/suci/suci.go en free5GC udm anterior a 1.2.0, cuando se usa Go anterior a 1.19, permite un Ataque de Curva no válida porque puede calcular un secreto compartido a través de una clave pública sin comprimir que no ha sido validada. Un atacante puede enviar SUCI arbitrarias a la UDM, que intenta descifrarlas tanto a través de su clave privada como de la clave pública del atacante. • https://github.com/free5gc/udm/compare/v1.1.1...v1.2.0 https://github.com/free5gc/udm/pull/20 https://www.gsma.com/security/wp-content/uploads/2023/10/0073-invalid_curve.pdf • CWE-347: Improper Verification of Cryptographic Signature •
CVSS: 7.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-39325 – HTTP/2 rapid reset can cause excessive work in net/http
https://notcve.org/view.php?id=CVE-2023-39325
A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing. With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection. • https://go.dev/cl/534215 https://go.dev/cl/534235 https://go.dev/issue/63417 https://groups.google.com/g/golang-announce/c/iNNxDTCjZvo/m/UDd7VKQuAAAJ https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3OVW5V2DM5K5IC3H7O42YDUGNJ74J35O https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3SZN67IL7HMGMNAVLOTIXLIHUDXZK4LH https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3WJ4QVX2AMUJ2F2S27POOAHRC4K3CHU4 https: • CWE-400: Uncontrolled Resource Consumption CWE-770: Allocation of Resources Without Limits or Throttling •