CVE-2018-1000211 Doorkeeper subject to Incorrect Permission Assignment
Attackers can retain valid access tokens for public OAuth apps because revocation fails, allowing unauthorized data access until expiry.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2018-1000211?
CVE-2018-1000211 is a high-severity missing authorization vulnerability in n/a, published on 13 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Doorkeeper version 4.2.0 and later contains a Incorrect Access Control vulnerability in Token revocation API's authorized method that can result in Access tokens are not revoked for public OAuth apps, leaking access until expiry.
Weakness: CWE-732
Which versions are affected by CVE-2018-1000211?
2 open source packages ship an affected version, including doorkeeper. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
doorkeeper RubyGems | From 4.2.0 | 4.4.0 |
doorkeeper RubyGems | From 4.2.0 | 4.4.0 |
Products include Doorkeeper Project Doorkeeper.
How do I fix CVE-2018-1000211?
Upgrade doorkeeper to 4.4.0 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2018-1000211 being exploited?
There is no known exploitation of CVE-2018-1000211 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2016-6582 Doorkeeper is vulnerable to replay attacks
- CVE-2020-10187 Exposure of Sensitive Information to an Unauthorized Actor in Doorkeeper
- CVE-2014-8144 Doorkeeper vulnerable to Cross-site Request Forgery
- CVE-2018-1000088 Doorkeeper is vulnerable to stored XSS and code execution
- CVE-2023-34246 Doorkeeper Improper Authentication vulnerability
Sources
Also known as DEBIAN-CVE-2018-1000211, GHSA-694m-jhr9-pf77, UBUNTU-CVE-2018-1000211.