{"answers":{"affected":"2 open source packages ship an affected version, including oauth2-server. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-18924 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-18924 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-18924 is a high-severity vulnerability in n/a, published on 4 Oct 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-2017-18924 and fix it if it is affected.\n\nWhat it is: CVE-2017-18924 is a high-severity vulnerability in n/a, published on 4 Oct 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-2017-18924 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- oauth2-server (npm): affected all versions up to 3.1.1; no fix listed\n- oauth2-server (npm): affected all versions up to 3.1.1; no fix listed\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-18924/ (Markdown: https://insights.sbomify.com/CVE-2017-18924/index.md)","id":"CVE-2017-18924","markdown":"https://insights.sbomify.com/CVE-2017-18924/index.md","name":"CVE-2017-18924","record":{"aliases":["GHSA-2fw4-mgq9-39cx"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js OAuth2 library","requires_auth":"none","summary":"The library lacks PKCE support, allowing authorization code injection attacks that could lead to account takeover.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"oauth2-server","vendor":"oauth2-server_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"oauth2-server (aka node-oauth2-server) through 3.1.1 implements OAuth 2.0 without PKCE. It does not prevent authorization code injection. This is similar to CVE-2020-7692. NOTE: the vendor states 'As RFC7636 is an extension, I think the claim in the Readme of \"RFC 6749 compliant\" is valid and not misleading and I also therefore wouldn't describe this as a \"vulnerability\" with the library per se.","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":false,"headline":"Code Injection in oauth2-server","id":"CVE-2017-18924","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2017"},"n_packages":2,"n_references":5,"next":{"headline":"Path traversal in n/a","id":"CVE-2017-18925"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["3.1.1"],"package":"oauth2-server","purl":null,"source":"GHSA-2fw4-mgq9-39cx"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["3.1.1"],"package":"oauth2-server","purl":"pkg:npm/oauth2-server","source":"GHSA-2fw4-mgq9-39cx"}],"prev":{"headline":"Path traversal in n/a","id":"CVE-2017-18923"},"products":["n/a"],"published":"2020-10-04","related":[{"cvss_score":7.2,"headline":"oauth2-server through 3.1.1 vulnerable to Open Redirect","id":"CVE-2020-26938","kev_date_added":null,"published":"2022-08-29"}],"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-05","vendors":["n/a"]},"summary":"The library lacks PKCE support, allowing authorization code injection attacks that could lead to account takeover.","url":"https://insights.sbomify.com/CVE-2017-18924/"}