{"answers":{"affected":"2 open source packages ship an affected version, including node-jose. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16007 in the wild and no public exploit code.","fix":"Upgrade node-jose to 0.9.3 or later.","what":"CVE-2017-16007 is a medium-severity vulnerability in HackerOne node-jose node module, published on 4 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-16007 and fix it if it is affected.\n\nWhat it is: CVE-2017-16007 is a medium-severity vulnerability in HackerOne node-jose node module, published on 4 Jun 2018. 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-2017-16007 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- node-jose (npm): affected all versions; fixed in 0.9.3\n- node-jose (npm): affected all versions; fixed in 0.9.3\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-2017-16007/ (Markdown: https://insights.sbomify.com/CVE-2017-16007/index.md)","id":"CVE-2017-16007","markdown":"https://insights.sbomify.com/CVE-2017-16007/index.md","name":"CVE-2017-16007","record":{"aliases":["GHSA-rvj9-8cvx-3vq9"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"JavaScript JOSE library","requires_auth":"none","summary":"An attacker can recover private keys via an invalid curve attack when using ECDH-ES encryption in the node-jose library.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"node-jose","vendor":"cisco"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"node-jose is a JavaScript implementation of the JSON Object Signing and Encryption (JOSE) for current web browsers and node.js-based servers. node-jose earlier than version 0.9.3 is vulnerable to an invalid curve attack. This allows an attacker to recover the private secret key when JWE with Key Agreement with Elliptic Curve Diffie-Hellman Ephemeral Static (ECDH-ES) is used.","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":"Invalid Curve Attack in node-jose","id":"CVE-2017-16007","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"weak_cryptography","year":"2017"},"n_packages":2,"n_references":4,"next":{"headline":"Cross-Site Scripting in i18next","id":"CVE-2017-16008"},"packages":[{"ecosystem":"npm","fixed":["0.9.3"],"introduced":["0"],"last_affected":[],"package":"node-jose","purl":null,"source":"GHSA-rvj9-8cvx-3vq9"},{"ecosystem":"npm","fixed":["0.9.3"],"introduced":["0"],"last_affected":[],"package":"node-jose","purl":"pkg:npm/node-jose","source":"GHSA-rvj9-8cvx-3vq9"}],"prev":{"headline":"XSS in Data URI in remarkable","id":"CVE-2017-16006"},"products":["node-jose node module"],"published":"2018-06-04","related":[{"cvss_score":7.5,"headline":"Improper calculations in ECC implementation can trigger a Denial-of-Service (DoS)","id":"CVE-2023-25653","kev_date_added":null,"published":"2023-02-16"},{"cvss_score":7.5,"headline":"Cisco node-jose improper validation of JWT signature","id":"CVE-2018-0114","kev_date_added":null,"published":"2018-01-04"}],"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-09-16","vendors":["HackerOne"]},"summary":"An attacker can recover private keys via an invalid curve attack when using ECDH-ES encryption in the node-jose library.","url":"https://insights.sbomify.com/CVE-2017-16007/"}