Vulnerability Details : CVE-2018-1000211
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.
Products affected by CVE-2018-1000211
- cpe:2.3:a:doorkeeper_project:doorkeeper:*:*:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2018-1000211
0.28%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 48 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2018-1000211
| Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
|---|---|---|---|---|---|---|
|
5.0
|
MEDIUM | AV:N/AC:L/Au:N/C:P/I:N/A:N |
10.0
|
2.9
|
NIST | |
|
7.5
|
HIGH | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
3.9
|
3.6
|
NIST |
CWE ids for CVE-2018-1000211
-
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.Assigned by: nvd@nist.gov (Primary)
References for CVE-2018-1000211
-
https://github.com/doorkeeper-gem/doorkeeper/issues/891
Revoking token does not work for public clients · Issue #891 · doorkeeper-gem/doorkeeper · GitHubThird Party Advisory
-
https://github.com/doorkeeper-gem/doorkeeper/pull/1119
Use Application#confidential? to determine revocation auth eligibility by f3ndot · Pull Request #1119 · doorkeeper-gem/doorkeeper · GitHubThird Party Advisory
Jump to