CVE-2017-18924
Oauth2-server Project Oauth2-server vulnerability
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 products
Oauth2-server. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Oauth2-server Project Oauth2-server runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/oauthjs/node-oauth2-server/pull/452 · Patch
- codeburst.io/missing-the-point-in-securing-oauth-2-0-83968708b467 · Third Party Advisory
- github.com/oauthjs/node-oauth2-server/issues/637 · Exploit
- tools.ietf.org/html/draft-ietf-oauth-security-topics-15 · Exploit
- tools.ietf.org/html/rfc7636 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2017-18924
- cve.org/CVERecord?id=CVE-2017-18924
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.