Advisory

GHSA-qcqv-38jg-2r43

Also known as: None

Summary

Pageflow vulnerable to insecure direct object reference in membership update endpoint

Details

Impact

Pageflow has a membership edit feature which allows users to edit the roles of user memberships associated with an account that they have the manager role to (including their own). While the Entity dropdown select field is greyed out in the UI, an attacker can use tools which allow sending arbitrary HTTP request to craft a request to the /admin/users/{user_id}/memberships/{membership_id} endpoint containing an additional membership[entity_id] parameter. This parameter is honored when the membership is updated, allowing an attacker to update the membership object associated with their own account (with manager role) to be associated with a different attacker-chosen account instead. Since account_ids are enumerable, an attacker can compromise all accounts present on the platform.

Mitigation

Upgrade to version 15.7.1 or 14.5.2 of the pageflow gem.

For more information

If you have any questions or comments about this advisory email us at info(at)codevise.de

Credits

Positive Security

Severity

High Basis: The source's own band: HIGH

Dates

Published
2022-09-15 03:21 UTC
Modified
2024-12-06 05:27 UTC

Affected packages and fixes

pageflow

RubyGems · All systems

Affected

  • introduced 0, fixed 14.5.2 (ecosystem)

Fixed versions

14.5.2

Fix

The export has no generic command for this ecosystem.

pageflow

RubyGems · All systems

Affected

  • introduced 15.0.0, fixed 15.7.1 (ecosystem)

Fixed versions

15.7.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