🚨 [security] Update jsrsasign 11.1.0 → 11.1.1 (patch)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ jsrsasign (11.1.0 → 11.1.1) · Repo · Changelog

Security Advisories 🚨

🚨 jsrsasign is vulnerable to DoS through Infinite Loop when processing zero or negative inputs

Versions of the package jsrsasign before 11.1.1 are vulnerable to Infinite loop via the bnModInverse function in ext/jsbn2.js when the BigInteger.modInverse implementation receives zero or negative inputs, allowing an attacker to hang the process permanently by supplying such crafted values (e.g., modInverse(0, m) or modInverse(-1, m)).

🚨 jsrsasign: Missing cryptographic validation during DSA signing enables private key extraction

Versions of the package jsrsasign before 11.1.1 are vulnerable to Missing Cryptographic Step via the KJUR.crypto.DSA.signWithMessageHash process in the DSA signing implementation. An attacker can recover the private key by forcing r or s to be zero, so the library emits an invalid signature without retrying, and then solves for x from the resulting signature.

🚨 jsrsasign: Incomplete Comparison Allows DSA Private Key Recovery via Biased Nonce Generation

Versions of the package jsrsasign from 7.0.0 and before 11.1.1 are vulnerable to Incomplete Comparison with Missing Factors via the getRandomBigIntegerZeroToMax and getRandomBigIntegerMinToMax functions in src/crypto-1.1.js; an attacker can recover the private key by exploiting the incorrect compareTo checks that accept out-of-range candidates and thus bias DSA nonces during signature generation.

🚨 jsrsasign: DSA signatures or X.509 certificates can be forged via DSA domain-parameter validation in KJUR.crypto.DSA.setPublic

Versions of the package jsrsasign before 11.1.1 are vulnerable to Improper Verification of Cryptographic Signature via the DSA domain-parameter validation in KJUR.crypto.DSA.setPublic (and the related DSA/X509 verification flow in src/dsa-2.0.js). An attacker can forge DSA signatures or X.509 certificates that X509.verifySignature() accepts by supplying malicious domain parameters such as g=1, y=1, and a fixed r=1, which make the verification equation true for any hash.

🚨 jsrsasign: Negative Exponent Handling Leads to Signature Verification Bypass

Versions of the package jsrsasign before 11.1.1 are vulnerable to Incorrect Conversion between Numeric Types due to handling negative exponents in ext/jsbn2.js. An attacker can force the computation of incorrect modular inverses and break signature verification by calling modPow with a negative exponent.

🚨 jsrsasign: Division by Zero Allows Invalid JWK Modulus to Cause Deterministic Zero Output in RSA Operations

Versions of the package jsrsasign before 11.1.1 are vulnerable to Division by zero due to the RSASetPublic/KEYUTIL parsing path in ext/rsa.js and the BigInteger.modPowInt reduction logic in ext/jsbn.js. An attacker can force RSA public-key operations (e.g., verify and encryption) to collapse to deterministic zero outputs and hide “invalid key” errors by supplying a JWK whose modulus decodes to zero.

Commits

See the full diff on Github. The new version differs by 22 commits:

• 11.1.1 release
• Merge pull request #641 from njg7194/add-security-policy
• Merge pull request #651 from Kr0emer/fix/bug-007-isprobableprime-negative
• Merge pull request #650 from Kr0emer/fix/bug-006-modpow-negative-exponent
• Merge pull request #647 from Kr0emer/fix/bug-003-dsa-nonce-compareto
• Merge pull request #646 from Kr0emer/fix/bug-002-dsa-domain-params-validation
• fix(crypto): correct compareTo checks in BigInteger RNG helpers
• fix(jsbn2): reject non-positive values in primality checks
• Merge branch 'master' into fix/bug-002-dsa-domain-params-validation
• Merge pull request #648 from Kr0emer/fix/bug-004-modinverse-dos
• test(crypto): move modPow negative-exponent tests away from RNG block
• Merge branch 'master' into fix/bug-004-modinverse-dos
• fix(jsbn2): handle negative exponents in BigInteger.modPow
• Merge pull request #649 from Kr0emer/fix/bug-005-rsa-zero-modulus
• Merge pull request #645 from Kr0emer/fix/bug-001-sign_s_zero
• fix(rsa): reject zero-modulus keys and fail on divide-by-zero
• fix(jsbn2): prevent modInverse hangs on zero and negative inputs
• fix(dsa): validate public domain parameters to prevent universal forgery
• fix(dsa): retry signing when r or s is zero
• docs: add SECURITY.md with security policy and best practices
• Merge pull request #639 from MaurizioPz/master
• Fix instanceof check for params array

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)