Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Medium severity, published 15 May 2024.
- Which products and versions are affected?
- FriendsOfSymfony UserBundle >= 1.0.0, < 1.2.1; friendsofsymfony/user-bundle (Packagist) >= 1.0.0, < 1.2.1.
- Is there a fix for This vulnerability?
- A patch was published on 2012-07-10: Date referenced in security advisory YAML for version 1.2.1 fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run FriendsOfSymfony UserBundle or friendsofsymfony/user-bundle (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is classified as Improper Authorization (CWE-285) within the user refreshing logic of FOSUserBundle. In affected versions, the bundle refreshed user sessions using the database primary key rather than the username. This creates a synchronization risk in scenarios where a user is permitted to change their username, potentially allowing a session to persist or be associated with incorrect identity data. The issue was resolved in version 1.2.1 by ensuring the user is loaded using the primary key correctly during the refreshing process to maintain identity integrity.
Affected products
- friendsofsymfony user-bundle >= 1.0.0, < 1.2.1
Timeline
- 2024-05-15: advisory: GitHub Advisory published
- 2012-07-10: patched: Date referenced in security advisory YAML for version 1.2.1 fix