{"api_version":"1","generated_at":"2026-07-23T04:16:23+00:00","cve":"CVE-2017-18924","urls":{"html":"https://cve.report/CVE-2017-18924","api":"https://cve.report/api/cve/CVE-2017-18924.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2017-18924","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2017-18924"},"summary":{"title":"CVE-2017-18924","description":"** DISPUTED ** 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.'","state":"PUBLIC","assigner":"cve@mitre.org","published_at":"2020-10-04 05:15:00","updated_at":"2023-11-07 02:41:00"},"problem_types":["CWE-94"],"metrics":[],"references":[{"url":"https://tools.ietf.org/html/rfc7636","name":"https://tools.ietf.org/html/rfc7636","refsource":"MISC","tags":["Third Party Advisory"],"title":"RFC 7636 - Proof Key for Code Exchange by OAuth Public Clients","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://github.com/oauthjs/node-oauth2-server/pull/452","name":"https://github.com/oauthjs/node-oauth2-server/pull/452","refsource":"MISC","tags":["Patch","Third Party Advisory"],"title":"PKCE by visvk · Pull Request #452 · oauthjs/node-oauth2-server · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://tools.ietf.org/html/draft-ietf-oauth-security-topics-15","name":"https://tools.ietf.org/html/draft-ietf-oauth-security-topics-15","refsource":"MISC","tags":["Exploit","Third Party Advisory"],"title":"draft-ietf-oauth-security-topics-15 - OAuth 2.0 Security Best Current Practice","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://github.com/oauthjs/node-oauth2-server/issues/637","name":"https://github.com/oauthjs/node-oauth2-server/issues/637","refsource":"MISC","tags":["Exploit","Third Party Advisory"],"title":"Multiple Security Vulnerabilities in Auth and Token Endpoint · Issue #637 · oauthjs/node-oauth2-server · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://codeburst.io/missing-the-point-in-securing-oauth-2-0-83968708b467","name":"https://codeburst.io/missing-the-point-in-securing-oauth-2-0-83968708b467","refsource":"MISC","tags":["Third Party Advisory"],"title":"Missing the Point in Securing OAuth 2.0 | by John Tucker | codeburst","mime":"text/html","httpstatus":"200","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-18924","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-18924","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2017","cve_id":"18924","vulnerable":"1","versionEndIncluding":"3.1.1","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"oauth2-server_project","cpe5":"oauth2-server","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"node.js","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[{"cve":"CVE-2017-18924","qid":"982722","title":"Nodejs (npm) Security Update for oauth2-server (GHSA-2fw4-mgq9-39cx)"}]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"cve@mitre.org","ID":"CVE-2017-18924","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"n/a","version":{"version_data":[{"version_value":"n/a"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"** DISPUTED ** 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.'"}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"url":"https://tools.ietf.org/html/rfc7636","refsource":"MISC","name":"https://tools.ietf.org/html/rfc7636"},{"url":"https://tools.ietf.org/html/draft-ietf-oauth-security-topics-15","refsource":"MISC","name":"https://tools.ietf.org/html/draft-ietf-oauth-security-topics-15"},{"url":"https://codeburst.io/missing-the-point-in-securing-oauth-2-0-83968708b467","refsource":"MISC","name":"https://codeburst.io/missing-the-point-in-securing-oauth-2-0-83968708b467"},{"url":"https://github.com/oauthjs/node-oauth2-server/issues/637","refsource":"MISC","name":"https://github.com/oauthjs/node-oauth2-server/issues/637"},{"url":"https://github.com/oauthjs/node-oauth2-server/pull/452","refsource":"MISC","name":"https://github.com/oauthjs/node-oauth2-server/pull/452"}]}},"nvd":{"publishedDate":"2020-10-04 05:15:00","lastModifiedDate":"2023-11-07 02:41:00","problem_types":["CWE-94"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"NONE","availabilityImpact":"NONE","baseScore":7.5,"baseSeverity":"HIGH"},"exploitabilityScore":3.9,"impactScore":3.6},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:L/Au:N/C:P/I:N/A:N","accessVector":"NETWORK","accessComplexity":"LOW","authentication":"NONE","confidentialityImpact":"PARTIAL","integrityImpact":"NONE","availabilityImpact":"NONE","baseScore":5},"severity":"MEDIUM","exploitabilityScore":10,"impactScore":2.9,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:oauth2-server_project:oauth2-server:*:*:*:*:*:node.js:*:*","versionEndIncluding":"3.1.1","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2017","CveId":"18924","Ordinal":"187969","Title":"CVE-2017-18924","CVE":"CVE-2017-18924","Year":"2017"},"notes":[{"CveYear":"2017","CveId":"18924","Ordinal":"1","NoteData":"** DISPUTED ** 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.'","Type":"Description","Title":null},{"CveYear":"2017","CveId":"18924","Ordinal":"2","NoteData":"2020-10-04","Type":"Other","Title":"Published"},{"CveYear":"2017","CveId":"18924","Ordinal":"3","NoteData":"2020-10-04","Type":"Other","Title":"Modified"}]}}}