Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings
CVE-2020-5275

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Firewall configured with unanimous strategy was not actually unanimous in Symfony

High severity GitHub Reviewed PublishedMar 30, 2020 in symfony/symfony • UpdatedFeb 5, 2024

Package

composersymfony/security (Composer)

Affected versions

>= 4.4.0, < 4.4.7
>= 5.0.0, < 5.0.7

Patched versions

4.4.7
5.0.7
composersymfony/security-http (Composer)
>= 4.4.0, < 4.4.7
>= 5.0.0, < 5.0.7
4.4.7
5.0.7
composersymfony/symfony (Composer)
>= 4.4.0, < 4.4.7
>= 5.0.0, < 5.0.7
4.4.7
5.0.7

Description

Description

On Symfony before 4.4.0, when aFirewall checks an access control rule (using the unanimous strategy), it iterates over all rule attributes and grant access only ifall calls to theaccessDecisionManager decide to grant access.

As of Symfony 4.4.0, a bug was introduced that prevents the check of attributes as soon asaccessDecisionManager decide to grant access on one attribute.

Resolution

TheaccessDecisionManager is now called with all attributes at once, allowing the unanimous strategy being applied on each attribute.

The patch for this issue is availablehere for the 4.4 branch.

Credits

I would like to thank Antonio J. García Lagar for reporting & Robin Chalas for fixing the issue.

References

@nicolas-grekasnicolas-grekas published to symfony/symfonyMar 30, 2020
ReviewedMar 30, 2020
Published to the GitHub Advisory DatabaseMar 30, 2020
Last updatedFeb 5, 2024

Severity

High

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
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
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:L/PR:L/UI:R/S:C/C:H/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided byFIRST.
(51st percentile)

Weaknesses

CVE ID

CVE-2020-5275

GHSA ID

GHSA-g4m9-5hpf-hx72

Source code

No known source code

Credits

LoadingChecking history
See something to contribute?Suggest improvements for this vulnerability.
[8]ページ先頭
©2009-2025 Movatter.jp