A critical cryptographic vulnerability in the jsrsasign library allows unauthenticated attackers to recover private keys, potentially leading to a total loss of confidentiality and integrity.

This vulnerability involves a missing cryptographic step within the KJUR.crypto.DSA.signWithMessageHash process. An unauthenticated attacker can force the library to emit invalid signatures by manipulating the r or s values, which enables the recovery of the private key.

The ability to recover private keys poses a severe risk to any application relying on this library for digital signatures or authentication. Successful exploitation grants an attacker the capability to impersonate legitimate users or sign malicious artifacts, resulting in a complete compromise of the trust chain and potential unauthorized access to protected resources. With a CVSS score of 8.7, this vulnerability represents a high-severity threat that necessitates immediate attention.

Immediate Action: Update the jsrsasign package to version 11.1.1 or later to implement the corrected DSA signing logic.

Proactive Monitoring: Monitor logs for unusual cryptographic errors or repeated signing failures that could indicate an attacker attempting to trigger the private key recovery process.

Compensating Controls: If immediate patching is not feasible, restrict access to services using affected signing functions and ensure that cryptographic keys are rotated if there is any suspicion of unauthorized access.

Public Exploit Available: Yes, a published PoC exists, attributed to the security researcher's technical write-up provided in the references.

The vulnerability in jsrsasign presents a significant risk to the security of digital signatures and identity verification processes. Security teams should prioritize the update to version 11.1.1 across all development and production environments. Failure to address this flaw leaves systems susceptible to cryptographic key theft, which can have long-lasting implications for data integrity and system security.