{"answers":{"affected":"2 open source packages ship an affected version, including jsrsasign. It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-14968 in the wild and no public exploit code.","fix":"Upgrade jsrsasign to 8.0.17 or later.","what":"CVE-2020-14968 is a critical vulnerability in n/a, published on 22 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-14968 and fix it if it is affected.\n\nWhat it is: CVE-2020-14968 is a critical vulnerability in n/a, published on 22 Jun 2020. 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-2020-14968 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- jsrsasign (npm): affected from 3.0.0; fixed in 8.0.17\n- jsrsasign (npm): affected from 3.0.0; fixed in 8.0.17\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-2020-14968/ (Markdown: https://insights.sbomify.com/CVE-2020-14968/index.md)","id":"CVE-2020-14968","markdown":"https://insights.sbomify.com/CVE-2020-14968/index.md","name":"CVE-2020-14968","record":{"aliases":["GHSA-q3gh-5r98-j4h3"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js crypto library","requires_auth":"none","summary":"The jsrsasign library fails to validate RSA-PSS signatures, allowing attackers to bypass signature checks or potentially trigger memory corruption.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jsrsasign","vendor":"kjur"},{"product":"max_data","vendor":"netapp"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"An issue was discovered in the jsrsasign package before 8.0.17 for Node.js. Its RSASSA-PSS (RSA-PSS) implementation does not detect signature manipulation/modification by prepending '\\0' bytes to a signature (it accepts these modified signatures as valid). An attacker can abuse this behavior in an application by creating multiple valid signatures where only one signature should exist. Also, an attacker might prepend these bytes with the goal of triggering memory corruption issues.","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-PSS signature validation vulnerability by prepending zeros in jsrsasign","id":"CVE-2020-14968","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2020"},"n_packages":2,"n_references":6,"next":{"headline":"Missing authorization in n/a","id":"CVE-2020-14969"},"packages":[{"ecosystem":"npm","fixed":["8.0.17"],"introduced":["3.0.0"],"last_affected":[],"package":"jsrsasign","purl":null,"source":"GHSA-q3gh-5r98-j4h3"},{"ecosystem":"npm","fixed":["8.0.17"],"introduced":["3.0.0"],"last_affected":[],"package":"jsrsasign","purl":"pkg:npm/jsrsasign","source":"GHSA-q3gh-5r98-j4h3"}],"prev":{"headline":"RSA PKCS#1 decryption vulnerability with prepending zeros in jsrsasign","id":"CVE-2020-14967"},"products":["n/a"],"published":"2020-06-22","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.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":9.1,"headline":"RSA signature validation vulnerability on maleable encoded message in jsrsasign","id":"CVE-2021-30246","kev_date_added":null,"published":"2021-04-07"},{"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-04","vendors":["n/a"]},"summary":"The jsrsasign library fails to validate RSA-PSS signatures, allowing attackers to bypass signature checks or potentially trigger memory corruption.","url":"https://insights.sbomify.com/CVE-2020-14968/"}