You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
node-jose is a JavaScript implementation of the JSON Object Signing and Encryption (JOSE) for web browsers and node.js-based servers. Prior to version 2.2.0, when using the non-default "fallback" crypto back-end, ECC operations in node-jose can trigger a Denial-of-Service (DoS) condition, due to a possible infinite loop in an internal calculation. For some ECC operations, this condition is triggered randomly; for others, it can be triggered by malicious input. The issue has been patched in version 2.2.0. Since this issue is only present in the "fallback" crypto implementation, it can be avoided by ensuring that either WebCrypto or the Node crypto module is available in the JS environment where node-jose is being run.
mend-for-github.aaakk.us.kgbot
changed the title
CVE-2023-25653 (High) detected in node-jose-2.1.1.tgz
CVE-2023-25653 (High) detected in node-jose-2.1.1.tgz - autoclosed
Feb 17, 2023
✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.
CVE-2023-25653 - High Severity Vulnerability
Vulnerable Library - node-jose-2.1.1.tgz
A JavaScript implementation of the JSON Object Signing and Encryption (JOSE) for current web browsers and node.js-based servers
Library home page: https://registry.npmjs.org/node-jose/-/node-jose-2.1.1.tgz
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
node-jose is a JavaScript implementation of the JSON Object Signing and Encryption (JOSE) for web browsers and node.js-based servers. Prior to version 2.2.0, when using the non-default "fallback" crypto back-end, ECC operations in
node-jose
can trigger a Denial-of-Service (DoS) condition, due to a possible infinite loop in an internal calculation. For some ECC operations, this condition is triggered randomly; for others, it can be triggered by malicious input. The issue has been patched in version 2.2.0. Since this issue is only present in the "fallback" crypto implementation, it can be avoided by ensuring that either WebCrypto or the Nodecrypto
module is available in the JS environment wherenode-jose
is being run.Publish Date: 2023-02-16
URL: CVE-2023-25653
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-5h4j-qrvg-9xhw
Release Date: 2023-02-16
Fix Resolution: node-jose - 2.2.0
The text was updated successfully, but these errors were encountered: