CVE-2017-18924
published 2020-10-04CVE-2017-18924: 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…
PriorityP342high7.5CVSS 3.1
AVNACLPRNUINSUCHINAN
EPSS
2.19%
80.4th percentile
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.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| oauth2-server_project | oauth2-server | <= 3.1.1 | — |
| oauth2-server_project | oauth2-server | 0 – 3.1.1 | — |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:N
ghsa9.1CRITICAL
osv9.1CRITICAL
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
Code Injection in oauth2-server
ghsa·2021-04-22·CVSS 9.1
CVE-2017-18924 [CRITICAL] CWE-94 Code Injection in oauth2-server
Code Injection in oauth2-server
"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.'"
OSV
Code Injection in oauth2-server
osv·2021-04-22·CVSS 9.1
CVE-2017-18924 [CRITICAL] Code Injection in oauth2-server
Code Injection in oauth2-server
"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.'"
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://codeburst.io/missing-the-point-in-securing-oauth-2-0-83968708b467https://github.com/oauthjs/node-oauth2-server/issues/637https://github.com/oauthjs/node-oauth2-server/pull/452https://tools.ietf.org/html/draft-ietf-oauth-security-topics-15https://tools.ietf.org/html/rfc7636https://codeburst.io/missing-the-point-in-securing-oauth-2-0-83968708b467https://github.com/oauthjs/node-oauth2-server/issues/637https://github.com/oauthjs/node-oauth2-server/pull/452https://tools.ietf.org/html/draft-ietf-oauth-security-topics-15https://tools.ietf.org/html/rfc7636
2020-10-04
Published