Skip to content

Commit e650ee1

Browse files
authored
Merge pull request #343 from f3ndot/CVE-2018-1000211
Add CVE-2018-1000211 for Doorkeeper
2 parents 2fd24d1 + e438262 commit e650ee1

1 file changed

Lines changed: 39 additions & 0 deletions

File tree

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
---
2+
gem: doorkeeper
3+
cve: 2018-1000211
4+
date: 2018-07-11
5+
url: "https://blog.justinbull.ca/cve-2018-1000211-public-apps-cant-revoke-tokens-in-doorkeeper/"
6+
7+
title: Doorkeeper gem does not revoke token for public clients
8+
9+
description: |
10+
Any OAuth application that uses public/non-confidential authentication when
11+
interacting with Doorkeeper is unable to revoke its tokens when calling the
12+
revocation endpoint.
13+
14+
A bug in the token revocation API would cause it to attempt to authenticate
15+
the public OAuth client as if it was a confidential app. Because of this, the
16+
token is never revoked.
17+
18+
The impact of this is the access or refresh token is not revoked, leaking
19+
access to protected resources for the remainder of that token's lifetime.
20+
21+
If Doorkeeper is used to facilitate public OAuth apps and leverage token
22+
revocation functionality, upgrade to the patched versions immediately.
23+
24+
Credit to Roberto Ostinelli for discovery, Justin Bull for the fixes.
25+
26+
DWF has assigned CVE-2018-1000211.
27+
28+
unaffected_versions:
29+
- "< 4.2.0"
30+
31+
patched_versions:
32+
- ">= 4.4.0"
33+
- ">= 5.0.0.rc2"
34+
35+
related:
36+
url:
37+
- https://github.com/doorkeeper-gem/doorkeeper/issues/891
38+
- https://github.com/doorkeeper-gem/doorkeeper/pull/1119
39+
- https://github.com/doorkeeper-gem/doorkeeper/pull/1120

0 commit comments

Comments
 (0)