Doorkeeper is vulnerable to stored XSS and code execution
Doorkeeper version 2.1.0 through 4.2.5 contains a Cross Site Scripting (XSS) vulnerability in web view's OAuth app form, user authorization prompt web view that can result in Stored XSS on the OAuth Client's name will cause users interacting with it will execute payload. This attack appear to be exploitable via The victim must be tricked to click an opaque link to the web view that runs the XSS payload. A malicious version virtually indistinguishable from a normal link. This vulnerability appears to have been fixed in 4.2.6, 4.3.0.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2018-1000088US | medium6.1 | — | ||
Doorkeeper version 2.1.0 through 4.2.5 contains a Cross Site Scripting (XSS) vulnerability in web view's OAuth app form, user authorization prompt web view that can result in Store… | ||||
references
External citations — patches, advisories, analysis.
- https://blog.justinbull.ca/cve-2018-1000088-stored-xss-in-doorkeeperWEB
- https://github.com/doorkeeper-gem/doorkeeperPACKAGE
- https://github.com/doorkeeper-gem/doorkeeper/commit/7b1a8373ecd69768c896000c7971dbf48948c1b5WEB
- https://github.com/doorkeeper-gem/doorkeeper/issues/969WEB
- https://github.com/doorkeeper-gem/doorkeeper/pull/970WEB
- https://github.com/doorkeeper-gem/doorkeeper/releases/tag/v4.3.0WEB
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/doorkeeper/CVE-2018-1000088.ymlWEB
- https://github.com/rubysec/ruby-advisory-db/pull/328/filesWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan