CVE-2022-24772 is a high-severity (CVSS 7.5) CWE-347 vulnerability in node-forge. A fix is available for node-forge — see the affected versions and patch details below.
Improper Verification of Cryptographic Signature in `node-forge`
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-24772 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
node-forgenpmDescription
Impact
RSA PKCS#1 v1.5 signature verification code does not check for tailing garbage bytes after decoding a DigestInfo ASN.1 structure. This can allow padding bytes to be removed and garbage data added to forge a signature when a low public exponent is being used.
Patches
The issue has been addressed in node-forge 1.3.0.
References
For more information, please see "Bleichenbacher's RSA signature forgery based on implementation error" by Hal Finney.
For more information
If you have any questions or comments about this advisory:
- Open an issue in forge
- Email us at example email address
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | node-forge | all versions | 1.3.0npm install node-forge@1.3.0 |
Affected Products
forgedigitalbazaarDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for node-forge, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update node-forge to 1.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24772 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This flaw affects the DigestInfo ASN.1 structure.
| Product | Fixed in | Advisory |
|---|---|---|
| OpenShift Service Mesh 2.1 | openshift-service-mesh/kiali-rhel8:1.36.9-1 | RHSA-2022:1739 |
| Red Hat OpenShift Data Foundation 4.11 on RHEL8 | odf4/mcg-core-rhel8:v4.11.0-30 | RHSA-2022:6156 |
| RHINT Service Registry 2.3.0 GA | node-forge | RHSA-2022:6835 |
| RHPAM 7.13.1 async | node-forge | RHSA-2022:6813 |
Frequently Asked Questions
Is CVE-2022-24772 in your dependencies?
Find it across npm, including transitive dependencies.