CVSS: 7.4EPSS: 0%CPEs: 1EXPL: 0CVE-2016-1000344 – bouncycastle: DHIES implementation allowed the use of ECB mode
https://notcve.org/view.php?id=CVE-2016-1000344
In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed from the provider. En la versión 1.55 y anteriores de Bouncy Castle JCE Provider, la implementación DHIES permitía el uso del modo ECB. Este modo se considera inseguro y el fabricante le ha retirado el soporte. • https://access.redhat.com/errata/RHSA-2018:2669 https://access.redhat.com/errata/RHSA-2018:2927 https://github.com/bcgit/bc-java/commit/9385b0ebd277724b167fe1d1456e3c112112be1f https://security.netapp.com/advisory/ntap-20181127-0004 https://www.oracle.com/security-alerts/cpuoct2020.html https://access.redhat.com/security/cve/CVE-2016-1000344 https://bugzilla.redhat.com/show_bug.cgi?id=1588314 • CWE-310: Cryptographic Issues CWE-325: Missing Cryptographic Step •
CVSS: 5.9EPSS: 0%CPEs: 2EXPL: 0CVE-2016-1000345 – bouncycastle: DHIES/ECIES CBC modes are vulnerable to padding oracle attack
https://notcve.org/view.php?id=CVE-2016-1000345
In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES/ECIES CBC mode vulnerable to padding oracle attack. For BC 1.55 and older, in an environment where timings can be easily observed, it is possible with enough observations to identify when the decryption is failing due to padding. En Bouncy Castle JCE Provider, en versiones 1.55 y anteriores, el modo DHIES/ECIES CBC es vulnerable a ataques de oráculo de relleno. Para BC 1.55 y anteriores, en un entorno en el que las sincronizaciones pueden observarse fácilmente, es posible identificar con la suficiente atención en qué punto falla el descifrado debido al relleno. • https://access.redhat.com/errata/RHSA-2018:2669 https://access.redhat.com/errata/RHSA-2018:2927 https://github.com/bcgit/bc-java/commit/21dcb3d9744c83dcf2ff8fcee06dbca7bfa4ef35#diff-4439ce586bf9a13bfec05c0d113b8098 https://lists.debian.org/debian-lts-announce/2018/07/msg00009.html https://security.netapp.com/advisory/ntap-20181127-0004 https://usn.ubuntu.com/3727-1 https://www.oracle.com/security-alerts/cpuoct2020.html https://access.redhat.com/security/cve/CVE-2016-1000345 https://bugzilla.redhat.com • CWE-325: Missing Cryptographic Step CWE-361: 7PK - Time and State •
CVSS: 4.8EPSS: 0%CPEs: 2EXPL: 0CVE-2016-1000346 – bouncycastle: Other party DH public keys are not fully validated
https://notcve.org/view.php?id=CVE-2016-1000346
In the Bouncy Castle JCE Provider version 1.55 and earlier the other party DH public key is not fully validated. This can cause issues as invalid keys can be used to reveal details about the other party's private key where static Diffie-Hellman is in use. As of release 1.56 the key parameters are checked on agreement calculation. En Bouncy Castle JCE Provider, en versiones 1.55 y anteriores, no se valida completamente la clave pública DH de la otra parte. Esto puede causar problemas, ya que las claves inválidas pueden emplearse para revelar detalles sobre la clave privada de la otra parte donde se emplea Diffie-Hellman estático. • https://access.redhat.com/errata/RHSA-2018:2669 https://access.redhat.com/errata/RHSA-2018:2927 https://github.com/bcgit/bc-java/commit/1127131c89021612c6eefa26dbe5714c194e7495#diff-d525a20b8acaed791ae2f0f770eb5937 https://lists.debian.org/debian-lts-announce/2018/07/msg00009.html https://security.netapp.com/advisory/ntap-20181127-0004 https://usn.ubuntu.com/3727-1 https://www.oracle.com/security-alerts/cpuoct2020.html https://access.redhat.com/security/cve/CVE-2016-1000346 https://bugzilla.redhat.com • CWE-320: Key Management Errors CWE-325: Missing Cryptographic Step •
CVSS: 7.4EPSS: 0%CPEs: 1EXPL: 0CVE-2016-1000352 – bouncycastle: ECIES implementation allowed the use of ECB mode
https://notcve.org/view.php?id=CVE-2016-1000352
In the Bouncy Castle JCE Provider version 1.55 and earlier the ECIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed from the provider. En la versión 1.55 y anteriores de Bouncy Castle JCE Provider, la implementación ECIES permitía el uso del modo ECB. Este modo se considera inseguro y el fabricante le ha retirado el soporte. • https://access.redhat.com/errata/RHSA-2018:2669 https://access.redhat.com/errata/RHSA-2018:2927 https://github.com/bcgit/bc-java/commit/9385b0ebd277724b167fe1d1456e3c112112be1f https://security.netapp.com/advisory/ntap-20181127-0004 https://www.oracle.com/security-alerts/cpuoct2020.html https://access.redhat.com/security/cve/CVE-2016-1000352 https://bugzilla.redhat.com/show_bug.cgi?id=1588330 • CWE-310: Cryptographic Issues CWE-325: Missing Cryptographic Step •
CVSS: 5.3EPSS: 0%CPEs: 2EXPL: 0CVE-2016-1000339 – bouncycastle: Information leak in AESFastEngine class
https://notcve.org/view.php?id=CVE-2016-1000339
In the Bouncy Castle JCE Provider version 1.55 and earlier the primary engine class used for AES was AESFastEngine. Due to the highly table driven approach used in the algorithm it turns out that if the data channel on the CPU can be monitored the lookup table accesses are sufficient to leak information on the AES key being used. There was also a leak in AESEngine although it was substantially less. AESEngine has been modified to remove any signs of leakage (testing carried out on Intel X86-64) and is now the primary AES class for the BC JCE provider from 1.56. Use of AESFastEngine is now only recommended where otherwise deemed appropriate. • https://access.redhat.com/errata/RHSA-2018:2669 https://access.redhat.com/errata/RHSA-2018:2927 https://github.com/bcgit/bc-java/commit/413b42f4d770456508585c830cfcde95f9b0e93b#diff-54656f860db94b867ba7542430cd2ef0 https://github.com/bcgit/bc-java/commit/8a73f08931450c17c749af067b6a8185abdfd2c0#diff-494fb066bed02aeb76b6c005632943f2 https://lists.debian.org/debian-lts-announce/2018/07/msg00009.html https://security.netapp.com/advisory/ntap-20181127-0004 https://usn.ubuntu.com/3727-1 https://www.oracle.com/security-alerts/cpuoc • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-310: Cryptographic Issues •