CVSS: 4.9EPSS: 0%CPEs: 1EXPL: 1CVE-2023-49292 – Possible private key restoration in go package github.com/ecies/go
https://notcve.org/view.php?id=CVE-2023-49292
ecies is an Elliptic Curve Integrated Encryption Scheme for secp256k1 in Golang. If funcations Encapsulate(), Decapsulate() and ECDH() could be called by an attacker, they could recover any private key that interacts with it. This vulnerability was patched in 2.0.8. Users are advised to upgrade. ecies es un esquema de cifrado integrado de curva elíptica para secp256k1 en Golang. Si un atacante pudiera llamar a las funciones Encapsulate(), Decapsulate() y ECDH(), podría recuperar cualquier clave privada que interactúe con ellas. • https://github.com/ashutosh1206/Crypton/blob/master/Diffie-Hellman-Key-Exchange/Attack-Invalid-Curve-Point/README.md https://github.com/ecies/go/commit/c6e775163866d6ea5233eb8ec8530a9122101ebd https://github.com/ecies/go/releases/tag/v2.0.8 https://github.com/ecies/go/security/advisories/GHSA-8j98-cjfr-qx3h • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
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: 83%CPEs: 444EXPL: 7CVE-2023-44487 – HTTP/2 Rapid Reset Attack Vulnerability
https://notcve.org/view.php?id=CVE-2023-44487
The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023. El protocolo HTTP/2 permite una denegación de servicio (consumo de recursos del servidor) porque la cancelación de solicitudes puede restablecer muchas transmisiones rápidamente, como se explotó en la naturaleza entre agosto y octubre de 2023. A flaw was found in handling multiplexed streams in the HTTP/2 protocol. A client can repeatedly make a request for a new multiplex stream and immediately send an RST_STREAM frame to cancel it. This creates extra work for the server setting up and tearing down the streams while not hitting any server-side limit for the maximum number of active streams per connection, resulting in a denial of service due to server resource consumption. • https://github.com/imabee101/CVE-2023-44487 https://github.com/studiogangster/CVE-2023-44487 https://github.com/bcdannyboy/CVE-2023-44487 https://github.com/sigridou/CVE-2023-44487- https://github.com/ByteHackr/CVE-2023-44487 https://github.com/ReToCode/golang-CVE-2023-44487 http://www.openwall.com/lists/oss-security/2023/10/13/4 http://www.openwall.com/lists/oss-security/2023/10/13/9 http://www.openwall.com/lists/oss-security/2023/10/18/4 http://www. • CWE-400: Uncontrolled Resource Consumption •