CVE-2017-18924 Code Injection in oauth2-server
The library lacks PKCE support, allowing authorization code injection attacks that could lead to account takeover.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2017-18924?
CVE-2017-18924 is a high-severity vulnerability in n/a, published on 4 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-94
Which versions are affected by CVE-2017-18924?
2 open source packages ship an affected version, including oauth2-server. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
oauth2-server npm | All versions to 3.1.1 | None |
oauth2-server npm | All versions to 3.1.1 | None |
Products include Oauth2-Server Project Oauth2-Server.
How do I fix CVE-2017-18924?
No fix has been published for CVE-2017-18924 yet. Limit exposure of the affected software until one is available.
Is CVE-2017-18924 being exploited?
There is no known exploitation of CVE-2017-18924 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-2fw4-mgq9-39cx.