{"answers":{"affected":"2 open source packages ship an affected version, including jsrsasign. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-30246 in the wild and no public exploit code.","fix":"Upgrade jsrsasign to 10.2.0 or later.","what":"CVE-2021-30246 is a critical vulnerability in n/a, published on 7 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-30246 and fix it if it is affected.\n\nWhat it is: CVE-2021-30246 is a critical vulnerability in n/a, published on 7 Apr 2021. 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-2021-30246 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- jsrsasign (npm): affected all versions; fixed in 10.2.0\n- jsrsasign (npm): affected all versions; fixed in 10.2.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-2021-30246/ (Markdown: https://insights.sbomify.com/CVE-2021-30246/index.md)","id":"CVE-2021-30246","markdown":"https://insights.sbomify.com/CVE-2021-30246/index.md","name":"CVE-2021-30246","record":{"aliases":["GHSA-27fj-mc8w-j9wg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js crypto library","requires_auth":"none","summary":"The jsrsasign library incorrectly validates certain invalid RSA signatures, potentially allowing attackers to bypass cryptographic verification mechanisms.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jsrsasign","vendor":"kjur"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"In the jsrsasign package through 10.1.13 for Node.js, some invalid RSA PKCS#1 v1.5 signatures are mistakenly recognized to be valid. NOTE: there is no known practical attack.","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":"RSA signature validation vulnerability on maleable encoded message in jsrsasign","id":"CVE-2021-30246","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":2,"n_references":3,"next":{"headline":"Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables","id":"CVE-2021-30254"},"packages":[{"ecosystem":"npm","fixed":["10.2.0"],"introduced":["0"],"last_affected":[],"package":"jsrsasign","purl":null,"source":"GHSA-27fj-mc8w-j9wg"},{"ecosystem":"npm","fixed":["10.2.0"],"introduced":["0"],"last_affected":[],"package":"jsrsasign","purl":"pkg:npm/jsrsasign","source":"GHSA-27fj-mc8w-j9wg"}],"prev":{"headline":"Code execution in Apache OpenOffice via non-http(s) schemes in Hyperlinks","id":"CVE-2021-30245"},"products":["n/a"],"published":"2021-04-07","related":[{"cvss_score":9.8,"headline":"RSA PKCS#1 decryption vulnerability with prepending zeros in jsrsasign","id":"CVE-2020-14967","kev_date_added":null,"published":"2020-06-22"},{"cvss_score":9.8,"headline":"RSA-PSS signature validation vulnerability by prepending zeros in jsrsasign","id":"CVE-2020-14968","kev_date_added":null,"published":"2020-06-22"},{"cvss_score":9.4,"headline":"jsrsasign: Missing cryptographic validation during DSA signing enables private key extraction","id":"CVE-2026-4601","kev_date_added":null,"published":"2026-03-23"},{"cvss_score":9.3,"headline":"jsrsasign: Incomplete Comparison Allows DSA Private Key Recovery via Biased Nonce Generation","id":"CVE-2026-4599","kev_date_added":null,"published":"2026-03-23"},{"cvss_score":9.1,"headline":"jsrsasign: DSA signatures or X.509 certificates can be forged via DSA domain-parameter validation in KJUR.crypto.DSA.setPublic","id":"CVE-2026-4600","kev_date_added":null,"published":"2026-03-23"},{"cvss_score":8.7,"headline":"jsrsasign is vulnerable to DoS through Infinite Loop when processing zero or negative inputs","id":"CVE-2026-4598","kev_date_added":null,"published":"2026-03-23"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"The jsrsasign library incorrectly validates certain invalid RSA signatures, potentially allowing attackers to bypass cryptographic verification mechanisms.","url":"https://insights.sbomify.com/CVE-2021-30246/"}