CVE-2017-18924

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2021-04-22. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
80.3%
KEV
Not listed

Published

October 4, 2020

Last Modified

November 21, 2024

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
npmoauth2-serverghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
oauth2-server

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 05:43 UTCEPSS rescore
  2. 2026-07-11 08:24 UTCEPSS rescore
  3. 2026-07-09 19:06 UTCEPSS rescore
  4. 2026-07-08 15:10 UTCEPSS rescore
  5. 2026-07-07 13:42 UTCEPSS rescore
  6. 2026-07-06 16:24 UTCEPSS rescore
  7. 2026-07-06 16:24 UTCEPSS rescore
  8. 2026-07-06 02:20 UTCEPSS rescore
  9. 2026-07-06 02:20 UTCEPSS rescore
  10. 2026-07-05 02:27 UTCEPSS rescore
  11. 2026-07-04 06:28 UTCEPSS rescore
  12. 2026-07-02 16:54 UTCEPSS rescore
  13. 2026-07-01 15:02 UTCEPSS rescore
  14. 2026-06-30 23:19 UTCEPSS rescore
  15. 2026-06-30 23:19 UTCEPSS rescore
  16. 2026-06-29 14:03 UTCEPSS rescore
  17. 2026-06-28 14:04 UTCEPSS rescore
  18. 2026-06-28 04:53 UTCEPSS rescore
  19. 2026-06-27 03:06 UTCEPSS rescore
  20. 2026-06-27 03:05 UTCEPSS rescore
  21. 2026-06-25 13:47 UTCEPSS rescore
  22. 2026-06-24 14:02 UTCEPSS rescore
  23. 2026-06-24 14:02 UTCEPSS rescore
  24. 2026-06-24 11:20 UTCOSV refresh
  25. 2026-06-23 21:30 UTCEPSS rescore
Show 47 more
  1. 2026-06-22 14:23 UTCEPSS rescore
  2. 2026-06-22 14:23 UTCEPSS rescore
  3. 2026-06-21 14:54 UTCEPSS rescore
  4. 2026-06-21 14:54 UTCEPSS rescore
  5. 2026-06-21 01:57 UTCEPSS rescore
  6. 2026-06-21 01:57 UTCEPSS rescore
  7. 2026-06-19 19:23 UTCEPSS rescore
  8. 2026-06-19 19:23 UTCEPSS rescore
  9. 2026-06-18 17:50 UTCEPSS rescore
  10. 2026-06-17 17:50 UTCEPSS rescore
  11. 2026-06-16 17:50 UTCEPSS rescore
  12. 2026-06-16 17:50 UTCEPSS rescore
  13. 2026-06-15 17:45 UTCEPSS rescore
  14. 2026-06-14 23:14 UTCEPSS rescore
  15. 2026-06-13 22:57 UTCEPSS rescore
  16. 2026-06-12 23:09 UTCEPSS rescore
  17. 2026-06-10 22:15 UTCEPSS rescore
  18. 2026-06-10 13:19 UTCEPSS rescore
  19. 2026-06-08 14:14 UTCEPSS rescore
  20. 2026-06-08 14:14 UTCEPSS rescore
  21. 2026-06-07 15:39 UTCOSV refresh
  22. 2026-06-07 15:22 UTCEPSS rescore
  23. 2026-06-07 15:22 UTCEPSS rescore
  24. 2026-06-06 13:45 UTCEPSS rescore
  25. 2026-06-06 13:45 UTCEPSS rescore
  26. 2026-06-05 22:44 UTCEPSS rescore
  27. 2026-06-05 06:08 UTCEPSS rescore
  28. 2026-06-05 06:08 UTCEPSS rescore
  29. 2026-06-04 13:10 UTCEPSS rescore
  30. 2026-06-02 20:11 UTCEPSS rescore
  31. 2026-06-02 20:11 UTCEPSS rescore
  32. 2026-06-01 13:49 UTCEPSS rescore
  33. 2026-05-31 22:28 UTCEPSS rescore
  34. 2026-05-31 22:28 UTCEPSS rescore
  35. 2026-05-31 00:14 UTCEPSS rescore
  36. 2026-05-31 00:14 UTCEPSS rescore
  37. 2026-05-29 13:41 UTCEPSS rescore
  38. 2026-05-28 13:42 UTCEPSS rescore
  39. 2026-05-28 13:42 UTCEPSS rescore
  40. 2026-05-27 13:38 UTCEPSS rescore
  41. 2026-05-27 13:38 UTCEPSS rescore
  42. 2026-05-26 13:42 UTCEPSS rescore
  43. 2026-05-26 13:42 UTCEPSS rescore
  44. 2026-05-26 07:17 UTCEPSS rescore
  45. 2026-05-26 07:17 UTCEPSS rescore
  46. 2026-05-23 07:02 UTCEG score recompute
  47. 2026-05-23 07:02 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2017-18924?
CVE-2017-18924 is a high vulnerability published on October 4, 2020. 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…
When was CVE-2017-18924 disclosed?
CVE-2017-18924 was first published in the National Vulnerability Database on October 4, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-18924 actively exploited?
CVE-2017-18924 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 80.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-18924?
CVE-2017-18924 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2017-18924?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-18924, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-18924

Explore →

Is Your Infrastructure Affected by CVE-2017-18924?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.