{"answers":{"affected":"2 open source packages ship an affected version, including jsrsasign.","exploited":"There is no known exploitation of GHSA-g753-jx37-7xwh in the wild and no public exploit code.","fix":"Upgrade jsrsasign to 8.0.13 or later.","what":"GHSA-g753-jx37-7xwh is a vulnerability in jsrsasign, published on 30 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 GHSA-g753-jx37-7xwh and fix it if it is affected.\n\nWhat it is: GHSA-g753-jx37-7xwh is a vulnerability in jsrsasign, published on 30 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 GHSA-g753-jx37-7xwh in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- jsrsasign (npm): affected from 4.0.0; fixed in 8.0.13\n- jsrsasign (npm): affected from 4.0.0; fixed in 8.0.13\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/GHSA-g753-jx37-7xwh/ (Markdown: https://insights.sbomify.com/GHSA-g753-jx37-7xwh/index.md)","id":"GHSA-g753-jx37-7xwh","markdown":"https://insights.sbomify.com/GHSA-g753-jx37-7xwh/index.md","name":"GHSA-g753-jx37-7xwh","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript crypto library","requires_auth":"none","summary":"An attacker can recover ECDSA private keys by analyzing timing variations during signature generation in the jsrsasign library.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\nECDSA side-channel attack named [Minerava](https://minerva.crocs.fi.muni.cz/) have been found and it was found that it affects to jsrsasign.\n\nExecution time of thousands signature generation have been observed then EC private key which is scalar value may be recovered since point and scalar multiplication time depends on bits of scalar. In jsrsasign 8.0.13 or later, execution time of EC point and scalar multiplication is almost constant and fixed for the issue.\n\n- Minerva is one of timing attack or side channel attack for EC.\n- If you don't use ECDSA class, you are not affected the vulnerability.\n- The vulnerability is that attacker may guess private key by checking processing time of EC key generation or ECDSA signing.\n- The cause issue is that point multiplication processing time in ECDSA signing is depends on private key value.\n- After 8.0.13, processing time of point multiplication in ECDSA signing have become constant for key value in theory.\n\n### Patches\nUsers using ECDSA signature generation should upgrade to 8.0.13 or later.\n\n### Workarounds\nThere is no workarounds in jsrsasign. Update jsrsasign or use other ECDSA library.\n\n### ACKNOWLEDGEMENT\nThanks to Jan Jancar @J08nY, Petr Svenda and Vladimir Sedlacek of Masaryk University in Czech Republic to find and report this vulnerability.\n\n### References\nhttps://minerva.crocs.fi.muni.cz/\nhttps://www.npmjs.com/advisories/1505\nhttps://github.com/kjur/jsrsasign/issues/411","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"ECDSA signature vulnerability of Minerva timing attack in jsrsasign","id":"GHSA-g753-jx37-7xwh","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["8.0.13"],"introduced":["4.0.0"],"last_affected":[],"package":"jsrsasign","purl":null,"source":"GHSA-g753-jx37-7xwh"},{"ecosystem":"npm","fixed":["8.0.13"],"introduced":["4.0.0"],"last_affected":[],"package":"jsrsasign","purl":"pkg:npm/jsrsasign","source":"GHSA-g753-jx37-7xwh"}],"products":null,"published":"2020-06-30","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An attacker can recover ECDSA private keys by analyzing timing variations during signature generation in the jsrsasign library.","url":"https://insights.sbomify.com/GHSA-g753-jx37-7xwh/"}