Daniel Bleichenbacher

**Name of the Vulnerable Software and Affected Versions** Elliptic versions prior to 6.6.2 **Description** The ECDSA implementation within the Elliptic package produces incorrect signatures when an interim value of `k` (calculated according to step 3.2 of RFC 6979) contains leading zeros, making it susceptible to cryptanalysis and potentially exposing the secret key. This occurs because the byte-length of `k` is calculated incorrectly, leading to truncation during computation. This can disrupt legitimate transactions or communications. An attacker, under specific conditions, could derive the secret key by obtaining both a faulty signature generated by a vulnerable version of Elliptic and a correct signature for the same inputs. **Recommendations** Update to Elliptic version 6.6.2 or later.

**Name of the Vulnerable Software and Affected Versions** Java SE versions 6u191, 7u181, 8u172, 10.0.1 Java SE Embedded version 8u171 JRockit version R28.3.18 **Description** A difficult to exploit vulnerability allows an unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded, JRockit. Successful attacks can result in unauthorized ability to cause a partial denial of service of Java SE, Java SE Embedded, JRockit. This vulnerability can be exploited through sandboxed Java Web Start applications and sandboxed Java applets, or by supplying data to APIs in the specified component without using sandboxed Java Web Start applications or sandboxed Java applets. **Recommendations** For Java SE versions 6u191, 7u181, 8u172, 10.0.1, update to a version that contains a fix for this issue. For Java SE Embedded version 8u171, update to a version that contains a fix for this issue. For JRockit version R28.3.18, update to a version that contains a fix for this issue. As a temporary workaround, consider restricting access to the Concurrency component to minimize the risk of exploitation. Avoid using the `Java Attach API` in the affected component until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Java SE version 10.0.1 **Description** The issue allows an unauthenticated attacker with network access via multiple protocols to compromise Java SE, resulting in unauthorized access to critical data or complete access to all Java SE accessible data. This can be exploited through sandboxed Java Web Start applications, sandboxed Java applets, or by supplying data to APIs in the specified component, such as through a web service. It applies to both client and server deployments of Java. **Recommendations** For Java SE version 10.0.1, consider disabling the use of sandboxed Java Web Start applications and sandboxed Java applets until a patch is available. Restrict access to APIs in the specified component to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** SSH Tectia Client/Server/Connector versions 5.1.0 and earlier SSH Tectia Manager versions 2.2.0 and earlier **Description** The issue allows remote attackers to forge a PKCS #1 v1.5 signature that is signed by an RSA key with exponent 3. This is due to the removal of PKCS-1 padding before generating a hash, which prevents correct verification of X.509 and other certificates that use PKCS #1. **Recommendations** For SSH Tectia Client/Server/Connector versions 5.1.0 and earlier, consider updating to a version that correctly handles PKCS-1 padding. For SSH Tectia Manager versions 2.2.0 and earlier, consider updating to a version that correctly handles PKCS-1 padding. As a temporary workaround, consider restricting the use of RSA keys with exponent 3 until a patch is available.

**Name of the Vulnerable Software and Affected Versions** Sun Solaris versions (affected versions not specified) Java JDK and JRE versions 5.0 Update 8 and earlier Java SDK and JRE versions 1.4.x up to 1.4.2 12 Java SDK and JRE versions 1.3.x up to 1.3.1 19 JSSE versions 1.0.3 03 and earlier IPSec/IKE (affected versions not specified) Secure Global Desktop (affected versions not specified) StarOffice (affected versions not specified) **Description** The issue allows remote attackers to forge a PKCS #1 v1.5 signature that is signed by an RSA key with exponent 3. This is because the affected products remove PKCS-1 padding before generating a hash, which prevents them from correctly verifying X.509 and other certificates that use PKCS #1. **Recommendations** For Java JDK and JRE versions 5.0 Update 8 and earlier, update to a version later than 5.0 Update 8. For Java SDK and JRE versions 1.4.x up to 1.4.2 12, update to a version later than 1.4.2 12. For Java SDK and JRE versions 1.3.x up to 1.3.1 19, update to a version later than 1.3.1 19. For JSSE versions 1.0.3 03 and earlier, update to a version later than 1.0.3 03. At the moment, there is no information about a newer version that contains a fix for this vulnerability for Sun Solaris, IPSec/IKE, Secure Global Desktop, and StarOffice.

Name of the Vulnerable Software and Affected Versions: GnuTLS versions prior to 1.4.4 Description: The issue concerns a problem with handling excess data in the digestAlgorithm.parameters field when generating a hash using an RSA key with exponent 3. This can be exploited remotely, allowing attackers to forge a PKCS #1 v1.5 signature that is signed by the RSA key. As a result, GnuTLS may fail to correctly verify X.509 and other certificates that use PKCS. Recommendations: For versions prior to 1.4.4, update to version 1.4.4 or later to resolve the issue. As a temporary workaround, consider restricting the use of RSA keys with exponent 3 until a patch is applied.