{"answers":{"affected":"2 open source packages ship an affected version, including node-forge. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-24771 in the wild and no public exploit code.","fix":"Upgrade node-forge to 1.3.0 or later.","what":"CVE-2022-24771 is a high-severity vulnerability in digitalbazaar forge, published on 18 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-24771 and fix it if it is affected.\n\nWhat it is: CVE-2022-24771 is a high-severity vulnerability in digitalbazaar forge, published on 18 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-24771 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- node-forge (npm): affected all versions; fixed in 1.3.0\n- node-forge (npm): affected all versions; fixed in 1.3.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-24771/ (Markdown: https://insights.sbomify.com/CVE-2022-24771/index.md)","id":"CVE-2022-24771","markdown":"https://insights.sbomify.com/CVE-2022-24771/index.md","name":"CVE-2022-24771","record":{"aliases":["DEBIAN-CVE-2022-24771","GHSA-cfm4-qjh2-4765","ROOT-APP-NPM-CVE-2022-24771","UBUNTU-CVE-2022-24771"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript cryptography library","requires_auth":"none","summary":"Attackers can forge RSA signatures in node-forge due to lenient PKCS#1 v1.5 verification, bypassing cryptographic integrity checks.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"forge","vendor":"digitalbazaar"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code is lenient in checking the digest algorithm structure. This can allow a crafted structure that steals padding bytes and uses unchecked portion of the PKCS#1 encoded message to forge a signature when a low public exponent is being used. The issue has been addressed in `node-forge` version 1.3.0. There are currently no known workarounds.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper Verification of Cryptographic Signature in node-forge","id":"CVE-2022-24771","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"weak_cryptography","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Improper Verification of Cryptographic Signature in `node-forge`","id":"CVE-2022-24772"},"packages":[{"ecosystem":"npm","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"node-forge","purl":null,"source":"GHSA-cfm4-qjh2-4765"},{"ecosystem":"npm","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"node-forge","purl":"pkg:npm/node-forge","source":"GHSA-cfm4-qjh2-4765"}],"prev":{"headline":"Improper Neutralization of Formula Elements in a CSV File in Gradio Flagging","id":"CVE-2022-24770"},"products":["forge"],"published":"2022-03-18","related":[{"cvss_score":9.8,"headline":"Prototype Pollution","id":"CVE-2020-7720","kev_date_added":null,"published":"2020-09-01"},{"cvss_score":8.7,"headline":"node-forge ASN.1 Unbounded Recursion","id":"CVE-2025-66031","kev_date_added":null,"published":"2025-11-26"},{"cvss_score":8.6,"headline":"CVE-2025-12816","id":"CVE-2025-12816","kev_date_added":null,"published":"2025-11-25"},{"cvss_score":7.5,"headline":"Forge has Denial of Service via Infinite Loop in BigInteger.modInverse() with Zero Input","id":"CVE-2026-33891","kev_date_added":null,"published":"2026-03-27"},{"cvss_score":7.5,"headline":"Forge has signature forgery in RSA-PKCS due to ASN.1 extra field","id":"CVE-2026-33894","kev_date_added":null,"published":"2026-03-27"},{"cvss_score":7.5,"headline":"Forge has signature forgery in Ed25519 due to missing S \u003e L check","id":"CVE-2026-33895","kev_date_added":null,"published":"2026-03-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["digitalbazaar"]},"summary":"Attackers can forge RSA signatures in node-forge due to lenient PKCS#1 v1.5 verification, bypassing cryptographic integrity checks.","url":"https://insights.sbomify.com/CVE-2022-24771/"}