Advisory

GHSA-25f5-gc4h-hc22

Also known as: CVE-2021-28680

Summary

Improper Privilege Management in devise_masquerade

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2021-12-08 19:55 UTC
Modified
2024-02-18 05:32 UTC

Affected packages and fixes

devise_masquerade

RubyGems · All systems

Affected

  • introduced 0, fixed 1.3.1 (ecosystem)

Fixed versions

1.3.1

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences