Skip to content

Authentication granted to all firewalls instead of just one

Moderate severity GitHub Reviewed Published Jun 17, 2021 in symfony/symfony • Updated Feb 5, 2024

Package

composer symfony/security-http (Composer)

Affected versions

>= 5.3.0, < 5.3.2

Patched versions

5.3.2
composer symfony/symfony (Composer)
>= 5.3.0, < 5.3.2
5.3.2

Description

Description

When an application defines multiple firewalls, the authenticated token delivered by one of the firewalls is available to all other firewalls. This can be abused when the application defines different providers for different parts of an application. In such a situation, a user authenticated on one part of the application is considered authenticated on the whole application.

Resolution

We now ensure that the authenticated token is only available for the firewall that generates it.

The patch for this issue is available here for branch 5.3.

Credits

I would like to thank Bogdan, gndk, Paweł Warchoł, Warxcell, and Adrien Lamotte for reporting the issue and Wouter J for fixing the issue.

References

@fabpot fabpot published to symfony/symfony Jun 17, 2021
Published by the National Vulnerability Database Jun 17, 2021
Reviewed Jun 18, 2021
Published to the GitHub Advisory Database Jun 21, 2021
Last updated Feb 5, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS score

0.193%
(58th percentile)

Weaknesses

CVE ID

CVE-2021-32693

GHSA ID

GHSA-rfcf-m67m-jcrq

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.