Axtls Project

axtls_project

8 CVEs • 1 product

Products (1)

Click to collapse

Toggle

CVEs (8)

CVE VENDORS PRODUCTS UPDATED PUBLISHED CVSS
CVE-2023-33613 1Axtls Project 1Axtls Jan 8, 2025 Jun 6, 2023 N/A· v4 5.5 MEDIUM· v3 N/A· v2 axTLS v2.1.5 was discovered to contain a heap buffer overflow in the bi_import function in axtls-code/crypto/bigint.c. This vulnerability allows attackers to cause a Denial of Service (DoS) when parsing a private key.
CVE-2019-9689 1Axtls Project 1Axtls Nov 21, 2024 Dec 3, 2019 N/A· v4 7.5 HIGH· v3 5.0 MEDIUM· v2 process_certificate in tls1.c in Cameron Hamilton-Rich axTLS through 2.1.5 has a Buffer Overflow via a crafted TLS certificate handshake message with zero certificates.
CVE-2019-10013 1Axtls Project 1Axtls Nov 21, 2024 Dec 3, 2019 N/A· v4 7.5 HIGH· v3 7.8 HIGH· v2 The asn1_signature function in asn1.c in Cameron Hamilton-Rich axTLS through 2.1.5 has a Buffer Overflow that allows remote attackers to cause a denial of service (memory and CPU consumption) via a crafted certificate in...Show more The asn1_signature function in asn1.c in Cameron Hamilton-Rich axTLS through 2.1.5 has a Buffer Overflow that allows remote attackers to cause a denial of service (memory and CPU consumption) via a crafted certificate in the TLS certificate handshake message, because the result of get_asn1_length() is not checked for a minimum or maximum size.Show less
CVE-2019-8981 1Axtls Project 1Axtls Nov 21, 2024 Mar 26, 2019 N/A· v4 9.8 CRITICAL· v3 7.5 HIGH· v2 tls1.c in Cameron Hamilton-Rich axTLS before 2.1.5 has a Buffer Overflow via a crafted sequence of TLS packets because the need_bytes value is mismanaged.
CVE-2018-16253 1Axtls Project 1Axtls Nov 21, 2024 Nov 7, 2018 N/A· v4 5.9 MEDIUM· v3 4.3 MEDIUM· v2 In sig_verify() in x509.c in axTLS version 2.1.3 and before, the PKCS#1 v1.5 signature verification does not properly verify the ASN.1 metadata. Consequently, a remote attacker can forge signatures when small public expo...Show more In sig_verify() in x509.c in axTLS version 2.1.3 and before, the PKCS#1 v1.5 signature verification does not properly verify the ASN.1 metadata. Consequently, a remote attacker can forge signatures when small public exponents are being used, which could lead to impersonation through fake X.509 certificates. This is an even more permissive variant of CVE-2006-4790 and CVE-2014-1568.Show less
CVE-2018-16150 1Axtls Project 1Axtls Nov 21, 2024 Nov 7, 2018 N/A· v4 5.9 MEDIUM· v3 4.3 MEDIUM· v2 In sig_verify() in x509.c in axTLS version 2.1.3 and before, the PKCS#1 v1.5 signature verification does not reject excess data after the hash value. Consequently, a remote attacker can forge signatures when small public...Show more In sig_verify() in x509.c in axTLS version 2.1.3 and before, the PKCS#1 v1.5 signature verification does not reject excess data after the hash value. Consequently, a remote attacker can forge signatures when small public exponents are being used, which could lead to impersonation through fake X.509 certificates. This is a variant of CVE-2006-4340.Show less
CVE-2018-16149 1Axtls Project 1Axtls Nov 21, 2024 Nov 7, 2018 N/A· v4 5.9 MEDIUM· v3 4.3 MEDIUM· v2 In sig_verify() in x509.c in axTLS version 2.1.3 and before, the PKCS#1 v1.5 signature verification blindly trusts the declared lengths in the ASN.1 structure. Consequently, when small public exponents are being used, a...Show more In sig_verify() in x509.c in axTLS version 2.1.3 and before, the PKCS#1 v1.5 signature verification blindly trusts the declared lengths in the ASN.1 structure. Consequently, when small public exponents are being used, a remote attacker can generate purposefully crafted signatures (and put them on X.509 certificates) to induce illegal memory access and crash the verifier.Show less
CVE-2017-1000416 1Axtls Project 1Axtls Nov 21, 2024 Jan 22, 2018 N/A· v4 5.3 MEDIUM· v3 5.0 MEDIUM· v2 axTLS version 1.5.3 has a coding error in the ASN.1 parser resulting in the year (19)50 of UTCTime being misinterpreted as 2050.