~/Bitcoin-Vulnerabilities$ ./attacksafe vulnerability_cve-2018-12437.sage
Buffer overflow vulnerability (CVE-2018-12437). In 2018, a buffer overflow vulnerability was discovered in the implementation of the SHAKE-128 hashing algorithm. This vulnerability could lead to arbitrary code execution and complete system compromise.
####################################################
~/Bitcoin-Vulnerabilities$ ./attacksafe vulnerability_cve-2019-14437.sage
Memory leak vulnerability (CVE-2019-14437). In 2019, a memory leak vulnerability was discovered in the implementation of the SHA-3 hashing algorithm. This vulnerability could lead to denial of service (DoS) and potential disclosure of sensitive information.
####################################################
~/Bitcoin-Vulnerabilities$ ./attacksafe vulnerability_cve-2016-1000339.sage
Vulnerability in the implementation of the RSA algorithm (CVE-2016-1000339). This vulnerability is due to an incorrect implementation of the RSA algorithm, which could lead to disclosure of the private key. The error is that the RSA key generation uses an insufficiently random number, which simplifies the task of factoring the RSA module.
####################################################
~/Bitcoin-Vulnerabilities$ ./attacksafe vulnerability_in_implementation_of_ecdsa_algorithm_cve-2016-1000343.sage
Vulnerability in the implementation of the ECDSA algorithm (CVE-2016-1000343). In this case, the fault lies in the incorrect implementation of the ECDSA key generation algorithm. An error may lead to the disclosure of the private key.
####################################################
~/Bitcoin-Vulnerabilities$ ./attacksafe vulnerability_in_implementation_of_tls_protocol_cve-2015-6644_cve-2015-7940.sage
Vulnerability in the implementation of the GCM algorithm (CVE-2016-1000352). This vulnerability is due to insufficient input validation when implementing the GCM encryption algorithm, which could lead to a plaintext selection attack.
####################################################
~/Bitcoin-Vulnerabilities$ ./attacksafe vulnerability_in_implementation_of_gcm_algorithm_cve-2016-1000352.sage
Vulnerability in the implementation of the GCM algorithm (CVE-2016-1000352). This vulnerability is due to insufficient input validation when implementing the GCM encryption algorithm, which could lead to a plaintext selection attack.
####################################################
~/Bitcoin-Vulnerabilities$ ./attacksafe vulnerability_in_implementation_of_poly1305.sage
Vulnerability in the implementation of Poly1305. In 2016, cryptography researchers Ismail Taghi, Ali Abbas, and Mohammad Tabari discovered a vulnerability in the implementation of the Poly1305 MAC function in NaCl. They found that by using some specially crafted messages, an attacker can cause a buffer overflow in Poly1305, leading to leakage of key information. This vulnerability was fixed in version 2016-07-13.
####################################################
~/Bitcoin-Vulnerabilities$ ./attacksafe vulnerability_in_implementation_of_salsa20_stream_cipher_in_nacl.sage
Vulnerability in the implementation of the Salsa20 stream cipher in NaCl
Salsa20 Nonce Reuse (2013)
In 2013, cryptography researcher Thai Duong discovered a vulnerability in NaCls implementation of the Salsa20 stream cipher. He found that in some cases the NaCl library reused some nonce values, which was against cryptographic guidelines and resulted in a vulnerability to replay attack. This vulnerability was fixed in version 2013-07-25.
####################################################
~/Bitcoin-Vulnerabilities$ ./attacksafe vulnerability_in_function_curve25519.sage
Cryptographic vulnerability in Curve25519 (2015)
In 2015, cryptography researchers Adam Langley and Adam Baker discovered a vulnerability in the Curve25519 algorithm used in NaCl. They discovered that if a private key was generated from an insufficient number of random bits, then an attacker could recover the private key using cryptographic attacks such as side-channel attacks. As of version 2015-05-19, NaCl requires that the private key contain at least 256 bits of random data.
Vulnerability in the Curve25519 function: In 2018, a vulnerability was discovered in the Curve25519 implementation of elliptic curves in NaCl. The bug allowed attackers to carry out a denial of service (DoS) attack or potentially compromise data confidentiality. The problem was quickly fixed by the developers and an updated version of the library was released to fix the vulnerability.
Rubber-hose bug (2015): This bug was discovered in the implementation of the Curve25519 cryptographic algorithm in the Elliptic library. The bug allowed an attacker to recover a private key from a public key, leaving all systems that use this algorithm for security vulnerable. Fortunately, the bug was discovered before it was actively exploited by attackers.
####################################################
~/Bitcoin-Vulnerabilities$ ./attacksafe vulnerability_cve-2019-17315.sage
Vulnerability CVE-2019-17315: In October 2019, a vulnerability was discovered related to the use of the SHA-256 cryptographic hashing function in the library. The vulnerability allowed an attacker to take control of the system on which the library was used by transmitting specially crafted data. This bug was fixed in version 1.0.18.
####################################################
