Symfony security-http up to 4.4.6/5.0.6 Rule improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Symfony security-http up to 4.4.6/5.0.6. This vulnerability affects unknown code of the component Rule Handler. The manipulation leads to improper authorization. This vulnerability is documented as CVE-2020-5275. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Symfony security-http up to 4.4.6/5.0.6. It has been rated as critical. This issue affects some unknown functionality of the component Rule Handler. The manipulation with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In symfony/security-http before versions 4.4.7 and 5.0.7, when a `Firewall` checks access control rule
The weakness was released 03/30/2020 (GitHub Repository). The advisory is shared at github.com. The identification of this vulnerability is CVE-2020-5275 since 01/02/2020. The attack may be initiated remotely. A simple authentication is required for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.
Upgrading to version 4.4.7 or 5.0.7 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.1
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.6
NVD Vector: 🔍
CNA Base Score: 7.6
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Improper authorizationCWE: CWE-285 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: security-http 4.4.7/5.0.7
Patch: github.com
Timeline
01/02/2020 🔍03/30/2020 🔍
03/31/2020 🔍
05/10/2025 🔍
Sources
Advisory: c935e4a3fba6cc2ab463a6ca382858068d63cebfStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2020-5275 (🔍)
GCVE (CVE): GCVE-0-2020-5275
GCVE (VulDB): GCVE-100-152441
Entry
Created: 03/31/2020 10:40Updated: 05/10/2025 02:07
Changes: 03/31/2020 10:40 (39), 03/31/2020 10:45 (11), 10/05/2020 10:18 (1), 05/12/2024 12:30 (18), 05/12/2024 12:37 (20), 05/10/2025 02:07 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.