CVSS: 4.3EPSS: 0%CPEs: 1EXPL: 0CVE-2016-8217
https://notcve.org/view.php?id=CVE-2016-8217
EMC RSA BSAFE Crypto-J versions prior to 6.2.2 has a PKCS#12 Timing Attack Vulnerability. A possible timing attack could be carried out by modifying a PKCS#12 file that has an integrity MAC for which the password is not known. An attacker could then feed the modified PKCS#12 file to the toolkit and guess the current MAC one byte at a time. This is possible because Crypto-J uses a non-constant-time method to compare the stored MAC with the calculated MAC. This vulnerability is similar to the issue described in CVE-2015-2601. • http://www.securityfocus.com/archive/1/540066/30/0/threaded http://www.securityfocus.com/bid/95831 http://www.securitytracker.com/id/1037732 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2016-8212
https://notcve.org/view.php?id=CVE-2016-8212
An issue was discovered in EMC RSA BSAFE Crypto-J versions prior to 6.2.2. There is an Improper OCSP Validation Vulnerability. OCSP responses have two time values: thisUpdate and nextUpdate. These specify a validity period; however, both values are optional. Crypto-J treats the lack of a nextUpdate as indicating that the OCSP response is valid indefinitely instead of restricting its validity for a brief period surrounding the thisUpdate time. • http://www.securityfocus.com/archive/1/540066/30/0/threaded http://www.securityfocus.com/bid/95831 http://www.securitytracker.com/id/1037732 • CWE-404: Improper Resource Shutdown or Release •
CVSS: 5.9EPSS: 0%CPEs: 7EXPL: 0CVE-2016-0887
https://notcve.org/view.php?id=CVE-2016-0887
EMC RSA BSAFE Micro Edition Suite (MES) 4.0.x and 4.1.x before 4.1.5, RSA BSAFE Crypto-C Micro Edition (CCME) 4.0.x and 4.1.x before 4.1.3, RSA BSAFE Crypto-J before 6.2.1, RSA BSAFE SSL-J before 6.2.1, and RSA BSAFE SSL-C before 2.8.9 allow remote attackers to discover a private-key prime by conducting a Lenstra side-channel attack that leverages an application's failure to detect an RSA signature failure during a TLS session. EMC RSA BSAFE Micro Edition Suite (MES) 4.0.x y 4.1.x en versiones anteriores a 4.1.5, RSA BSAFE Crypto-C Micro Edition (CCME) 4.0.x y 4.1.x en versiones anteriores a 4.1.3, RSA BSAFE Crypto-J en versiones anteriores a 6.2.1, RSA BSAFE SSL-J en versiones anteriores a 6.2.1 y RSA BSAFE SSL-C en versiones anteriores a 2.8.9 permiten a atacantes remotos descubrir un factor primo de clave privada llevando a cabo un ataque Lenstra de canal lateral que aprovecha el fallo de una aplicación para detectar un fallo de firma RSA durante una sesión TLS. • http://packetstormsecurity.com/files/136656/RSA-BSAFE-Lenstras-Attack.html http://seclists.org/bugtraq/2016/Apr/66 http://www.securityfocus.com/archive/1/538055/100/0/threaded http://www.securitytracker.com/id/1035515 http://www.securitytracker.com/id/1035516 http://www.securitytracker.com/id/1035517 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVSS: 5.8EPSS: 0%CPEs: 3EXPL: 0CVE-2007-6755
https://notcve.org/view.php?id=CVE-2007-6755
The NIST SP 800-90A default statement of the Dual Elliptic Curve Deterministic Random Bit Generation (Dual_EC_DRBG) algorithm contains point Q constants with a possible relationship to certain "skeleton key" values, which might allow context-dependent attackers to defeat cryptographic protection mechanisms by leveraging knowledge of those values. NOTE: this is a preliminary CVE for Dual_EC_DRBG; future research may provide additional details about point Q and associated attacks, and could potentially lead to a RECAST or REJECT of this CVE. El procedimiento por defecto del NIST SP 800-90A del algoritmo Dual Elliptic Curve Deterministic Random Bit Generation (Dual_EC_DRBG) contiene puntos constantes Q con una posible relación con ciertos valores "skeleton key", lo que podría permitir a atacantes dependientes del contexto romper mecanismos criptográficos de protección mediante el aprovechando del conocimiento de esos valores. NOTA: este es un CVE preliminar para Dual_EC_DRBG, la investigación futura puede brindar detalles adicionales sobre el punto Q y los ataques asociados, y podría potencialmente dar lugar a un RECAST o REJECT de esta CVE. • http://arstechnica.com/security/2013/09/stop-using-nsa-influence-code-in-our-product-rsa-tells-customers http://blog.cryptographyengineering.com/2013/09/rsa-warns-developers-against-its-own.html http://blog.cryptographyengineering.com/2013/09/the-many-flaws-of-dualecdrbg.html http://rump2007.cr.yp.to/15-shumow.pdf http://stream.wsj.com/story/latest-headlines/SS-2-63399/SS-2-332655 http://threatpost.com/in-wake-of-latest-crypto-revelations-everything-is-suspect http://www.securityfocus.com/bid • CWE-327: Use of a Broken or Risky Cryptographic Algorithm •