CVSS: 5.3EPSS: 0%CPEs: 7EXPL: 0CVE-2020-7041
https://notcve.org/view.php?id=CVE-2020-7041
27 Feb 2020 — An issue was discovered in openfortivpn 1.11.0 when used with OpenSSL 1.0.2 or later. tunnel.c mishandles certificate validation because an X509_check_host negative error code is interpreted as a successful return value. Se detectó un problema en openfortivpn versión 1.11.0, cuando se usaba con OpenSSL versiones 1.0.2 o posteriores, el archivo tunnel.c maneja inapropiadamente la comprobación del certificado porque un código de error negativo de X509_check_host se interpreta como un valor de retorno exitoso. • http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00009.html • CWE-295: Improper Certificate Validation •
CVSS: 5.3EPSS: 4%CPEs: 18EXPL: 0CVE-2019-1551 – rsaz_512_sqr overflow bug on x86_64
https://notcve.org/view.php?id=CVE-2019-1551
06 Dec 2019 — There is an overflow bug in the x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against 2-prime RSA1024, 3-prime RSA1536, and DSA1024 as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH512 are considered just feasible. However, for an attack the target would have to re-use the DH512 private key, which is not recommended anyway. • http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00030.html • CWE-190: Integer Overflow or Wraparound •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2019-1547 – ECDSA remote timing attack
https://notcve.org/view.php?id=CVE-2019-1547
10 Sep 2019 — Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key r... • http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00054.html • CWE-602: Client-Side Enforcement of Server-Side Security •
CVSS: 5.3EPSS: 1%CPEs: 1EXPL: 0CVE-2019-1549 – Fork Protection
https://notcve.org/view.php?id=CVE-2019-1549
10 Sep 2019 — OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an applicati... • https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=1b0fe00e2704b5e20334a16d3c9099d1ba2ef1be • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-330: Use of Insufficiently Random Values •
CVSS: 4.3EPSS: 1%CPEs: 3EXPL: 0CVE-2019-1563 – Padding Oracle in PKCS7_dataDecode and CMS_decrypt_set1_pkey
https://notcve.org/view.php?id=CVE-2019-1563
10 Sep 2019 — In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to selec... • http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00054.html • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-203: Observable Discrepancy CWE-327: Use of a Broken or Risky Cryptographic Algorithm •
CVSS: 9.8EPSS: 0%CPEs: 1EXPL: 0CVE-2018-20997
https://notcve.org/view.php?id=CVE-2018-20997
26 Aug 2019 — An issue was discovered in the openssl crate before 0.10.9 for Rust. A use-after-free occurs in CMS Signing. Se descubrió un problema e el paquete openssl antes de 0.10.9 para Rust. Se produce un uso libre después de la firma de CMS. • https://rustsec.org/advisories/RUSTSEC-2018-0010.html • CWE-416: Use After Free •
CVSS: 8.1EPSS: 0%CPEs: 1EXPL: 0CVE-2016-10931
https://notcve.org/view.php?id=CVE-2016-10931
26 Aug 2019 — An issue was discovered in the openssl crate before 0.9.0 for Rust. There is an SSL/TLS man-in-the-middle vulnerability because certificate verification is off by default and there is no API for hostname verification. Se detectó un problema en el paquete openssl versiones anteriores a 0.9.0 para Rust. Presenta una vulnerabilidad de tipo man-in-the-middle de SSL/TLS porque la comprobación del certificado está desactivada por defecto y no existe API para la comprobación del nombre del host. • https://rustsec.org/advisories/RUSTSEC-2016-0001.html • CWE-295: Improper Certificate Validation •
CVSS: 3.3EPSS: 0%CPEs: 3EXPL: 0CVE-2019-1552 – Windows builds with insecure path defaults
https://notcve.org/view.php?id=CVE-2019-1552
30 Jul 2019 — OpenSSL has internal defaults for a directory tree where it can find a configuration file as well as certificates used for verification in TLS. This directory is most commonly referred to as OPENSSLDIR, and is configurable with the --prefix / --openssldir configuration options. For OpenSSL versions 1.1.0 and 1.1.1, the mingw configuration targets assume that resulting programs and libraries are installed in a Unix-like environment and the default prefix for program installation as well as for OPENSSLDIR sho... • https://cert-portal.siemens.com/productcert/pdf/ssa-412672.pdf • CWE-295: Improper Certificate Validation •
CVSS: 7.4EPSS: 3%CPEs: 2EXPL: 0CVE-2019-1543 – ChaCha20-Poly1305 with long nonces
https://notcve.org/view.php?id=CVE-2019-1543
06 Mar 2019 — ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any additional leading bytes are ignored. • http://lists.opensuse.org/opensuse-security-announce/2019-07/msg00056.html • CWE-323: Reusing a Nonce, Key Pair in Encryption CWE-327: Use of a Broken or Risky Cryptographic Algorithm CWE-330: Use of Insufficiently Random Values •
CVSS: 5.9EPSS: 6%CPEs: 180EXPL: 0CVE-2019-1559 – 0-byte record padding oracle
https://notcve.org/view.php?id=CVE-2019-1559
26 Feb 2019 — If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a close_notify, and once to receive one) then OpenSSL can respond differently to the calling application if a 0 byte record is received with invalid padding compared to if a 0 byte record is received with an invalid MAC. If the application then behaves differently based on that in a way that is detectable to the remote peer, then this amounts to a padding oracle that could be used to decrypt data. In order ... • http://lists.opensuse.org/opensuse-security-announce/2019-03/msg00041.html • CWE-203: Observable Discrepancy CWE-325: Missing Cryptographic Step •