Snyk test report

CVE-2024-9143

---

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.20 relevant fixed versions and status.

Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes.

Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low.

In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding.

The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions.

Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Remediation

Upgrade Alpine:3.20 openssl to version 3.3.2-r3 or higher.

References

• https://github.com/openssl/openssl/commit/72ae83ad214d2eef262461365a1975707f862712
• https://github.com/openssl/openssl/commit/bc7e04d7c8d509fb78fc0e285aa948fb0da04700
• https://github.com/openssl/openssl/commit/c0d3e4d32d2805f49bec30547f225bc4d092e1f4
• https://github.com/openssl/openssl/commit/fdf6723362ca51bd883295efe206cb5b1cfa5154
• https://github.openssl.org/openssl/extended-releases/commit/8efc0cbaa8ebba8e116f7b81a876a4123594d86a
• https://github.openssl.org/openssl/extended-releases/commit/9d576994cec2b7aa37a91740ea7e680810957e41
• https://openssl-library.org/news/secadv/20241016.txt
• http://www.openwall.com/lists/oss-security/2024/10/16/1
• http://www.openwall.com/lists/oss-security/2024/10/23/1
• http://www.openwall.com/lists/oss-security/2024/10/24/1
• https://security.netapp.com/advisory/ntap-20241101-0001/

---

CVE-2024-13176

---

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.20 relevant fixed versions and status.

Issue summary: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation.

Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measuring the timing would require either local access to the signing application or a very fast network connection with low latency.

There is a timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This can happen with significant probability only for some of the supported elliptic curves. In particular the NIST P-521 curve is affected. To be able to measure this leak, the attacker process must either be located in the same physical computer or must have a very fast network connection with low latency. For that reason the severity of this vulnerability is Low.

Remediation

Upgrade Alpine:3.20 openssl to version 3.3.2-r2 or higher.

References

• https://github.com/openssl/openssl/commit/07272b05b04836a762b4baa874958af51d513844
• https://github.com/openssl/openssl/commit/2af62e74fb59bc469506bc37eb2990ea408d9467
• https://github.com/openssl/openssl/commit/392dcb336405a0c94486aa6655057f59fd3a0902
• https://github.com/openssl/openssl/commit/4b1cb94a734a7d4ec363ac0a215a25c181e11f65
• https://github.com/openssl/openssl/commit/77c608f4c8857e63e98e66444e2e761c9627916f
• https://github.openssl.org/openssl/extended-releases/commit/0d5fd1ab987f7571e2c955d8d8b638fc0fb54ded
• https://github.openssl.org/openssl/extended-releases/commit/a2639000db19878d5d89586ae7b725080592ae86
• https://openssl-library.org/news/secadv/20250120.txt
• http://www.openwall.com/lists/oss-security/2025/01/20/2
• https://security.netapp.com/advisory/ntap-20250124-0005/

---

CVE-2024-12797

---

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.20 relevant fixed versions and status.

Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode is set.

Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by clients.

RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate chain. The affected clients are those that then rely on the handshake to fail when the server's RPK fails to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER.

Clients that enable server-side raw public keys can still find out that raw public key verification failed by calling SSL_get_verify_result(), and those that do, and take appropriate action, are not affected. This issue was introduced in the initial implementation of RPK support in OpenSSL 3.2.

The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Remediation

Upgrade Alpine:3.20 openssl to version 3.3.3-r0 or higher.

References

• https://github.com/openssl/openssl/commit/738d4f9fdeaad57660dcba50a619fafced3fd5e9
• https://github.com/openssl/openssl/commit/798779d43494549b611233f92652f0da5328fbe7
• https://github.com/openssl/openssl/commit/87ebd203feffcf92ad5889df92f90bb0ee10a699
• https://openssl-library.org/news/secadv/20250211.txt
• http://www.openwall.com/lists/oss-security/2025/02/11/3
• http://www.openwall.com/lists/oss-security/2025/02/11/4
• https://security.netapp.com/advisory/ntap-20250214-0001/

---

CVE-2025-26519

---

NVD Description

Note: Versions mentioned in the description apply only to the upstream musl package and not the musl package as distributed by Alpine. See How to fix? for Alpine:3.20 relevant fixed versions and status.

musl libc 0.9.13 through 1.2.5 before 1.2.6 has an out-of-bounds write vulnerability when an attacker can trigger iconv conversion of untrusted EUC-KR text to UTF-8.

Remediation

Upgrade Alpine:3.20 musl to version 1.2.5-r1 or higher.

References

• https://git.musl-libc.org/cgit/musl/commit/?id=c47ad25ea3b484e10326f933e927c0bc8cded3da
• https://git.musl-libc.org/cgit/musl/commit/?id=e5adcd97b5196e29991b524237381a0202a60659
• https://www.openwall.com/lists/oss-security/2025/02/13/2
• http://www.openwall.com/lists/oss-security/2025/02/13/2
• http://www.openwall.com/lists/oss-security/2025/02/13/3
• http://www.openwall.com/lists/oss-security/2025/02/13/4
• http://www.openwall.com/lists/oss-security/2025/02/13/5
• http://www.openwall.com/lists/oss-security/2025/02/14/5
• http://www.openwall.com/lists/oss-security/2025/02/14/6

---