Daniel Bleichenbacher

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.

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.

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.

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.

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.

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.