Authentication Bypass in Devise
An issue was discovered in Plataformatec Devise before 4.7.1. It confirms accounts upon receiving a request with a blank confirmation_token, if a database record has a blank value in the confirmation_token column. (However, there is no scenario within Devise itself in which such database records would exist.)
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-16109US | medium5.3 | — | ||
An issue was discovered in Plataformatec Devise before 4.7.1. It confirms accounts upon receiving a request with a blank confirmation_token, if a database record has a blank value… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/plataformatec/devisePACKAGE
- https://github.com/plataformatec/devise/compare/v4.7.0...v4.7.1WEB
- https://github.com/plataformatec/devise/issues/5071WEB
- https://github.com/plataformatec/devise/pull/5132WEB
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/devise/CVE-2019-16109.ymlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2019-16109ADVISORY
scry
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