Advisory

GHSA-7mx2-7q8p-pgmw

Also known as: None

Summary

Symfony may allow a user to switch to using another user's identity

Details

Symfony 2.0.6 has just been released. It addresses a security vulnerability in the EntityUserProvider as provided in the Doctrine bridge.

If you let your users update their login/username from a form, and if you are using Doctrine as a user provider, then you are vulnerable and you should upgrade as soon as possible.

The issue is that it is possible for a user to switch to another one. Here is how to reproduce it: The current user changes its username via a form to another existing username. When the form is submitted, he will have a validation error (as the username already exists) but the user object in the session will still be modified to the new username. This user from the session will be used for the next requests and so the user will be switched to this other user.

The fix is to always refresh the user via the primary key (which cannot be updated via a form) instead of the username.

If you cannot upgrade immediately, please apply the following patch: https://github.com/symfony/symfony/commit/9d2ab9ca9c1762

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-05-30 00:56 UTC
Modified
2024-12-04 05:40 UTC

Affected packages and fixes

symfony/symfony

Packagist · All systems

Affected

  • introduced 2.0.0, fixed 2.0.6 (ecosystem)

Fixed versions

2.0.6

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