CVE-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 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.
Code Injection
ProviderTypeBase ScoreAtk. VectorAtk. ComplexityPriv. RequiredVector
NISTNIST
7.5 HIGH
NETWORK
LOW
NONE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
mitreCNA
---
---
CVEADP
---
---
Base Score
CVSS 3.x
EPSS Score
Percentile: 41%
VendorProductVersion
oauth2-server_projectoauth2-server
𝑥
≤ 3.1.1
𝑥
= Vulnerable software versions
Common Weakness Enumeration
References
https://codeburst.io/missing-the-point-in-securing-oauth-2-0-83968708b467
https://github.com/oauthjs/node-oauth2-server/issues/637
https://github.com/oauthjs/node-oauth2-server/pull/452
https://tools.ietf.org/html/draft-ietf-oauth-security-topics-15
https://tools.ietf.org/html/rfc7636
https://codeburst.io/missing-the-point-in-securing-oauth-2-0-83968708b467
https://github.com/oauthjs/node-oauth2-server/issues/637
https://github.com/oauthjs/node-oauth2-server/pull/452
https://tools.ietf.org/html/draft-ietf-oauth-security-topics-15
https://tools.ietf.org/html/rfc7636