The devise_masquerade gem before 1.3 allows certain attacks when a password's salt is unknown. An application that uses this gem to let administrators masquerade/impersonate users loses one layer of security protection compared to a situation where Devise (without this extension) is used. If the server-side secret_key_base value became publicly known (for instance if it is committed to a public repository by mistake), there are still other protections in place that prevent an attacker from impersonating any user on the site. When masquerading is not used in a plain Devise application, one must know the password salt of the target user if one wants to encrypt and sign a valid session cookie. When devise_masquerade is used, however, an attacker can decide which user the "back" action will go back to without knowing that user's password salt and simply knowing the user ID, by manipulating the session cookie and pretending that a user is already masqueraded by an administrator.
References
| Link | Resource |
|---|---|
| https://github.com/oivoodoo/devise_masquerade/issues/83 | Issue Tracking Third Party Advisory |
| https://labanskoller.se/blog/2021/03/23/the-devise-extension-that-peeled-off-one-layer-of-the-security-onion-cve-2021-28680/ | Exploit Third Party Advisory |
Configurations
History
No history.
Information
Published : 2021-12-07 21:15
Updated : 2024-02-28 18:48
NVD link : CVE-2021-28680
Mitre link : CVE-2021-28680
CVE.ORG link : CVE-2021-28680
JSON object : View
Products Affected
devise_masquerade_project
- devise_masquerade
CWE