CVE-2017-11365 — Vulnerability in symfony/security — CVE Details
Symfony Incorrect Access Control
Summary
Advisory Timeline
- First published May 24, 2022 (1602 days ago).
- Last revised February 16, 2024 — 633 days after initial publication.
Remediation
Upgrade to the fixed version using your package manager.
composer require "symfony/security:^2.7.32"
composer require "symfony/security:^3.2.12"
composer require "symfony/symfony:^3.2.12"
composer require "symfony/security-core:^3.3.5"
composer require "symfony/security:^2.8.25"
composer require "symfony/symfony:^2.8.25"
composer require "symfony/security-core:^2.7.32"
composer require "symfony/security-core:^3.2.12"
composer require "symfony/security-core:^2.8.25"
composer require "symfony/symfony:^3.3.5"
composer require "symfony/symfony:^2.7.32"
composer require "symfony/security:^3.3.5"
After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.
Affected Packages (12)
Affects 1 ecosystem: packagist (3).
| Package | Ecosystem | Affected | Fixed In |
|---|---|---|---|
| symfony/security | packagist | v2.7.30, v2.7.31 | 2.7.32 |
| symfony/security | packagist | v3.2.10, v3.2.11 | 3.2.12 |
| symfony/symfony | packagist | v3.2.10, v3.2.11 | 3.2.12 |
| symfony/security-core | packagist | v3.3.3, v3.3.4 | 3.3.5 |
| symfony/security | packagist | v2.8.23, v2.8.24 | 2.8.25 |
| symfony/symfony | packagist | v2.8.23, v2.8.24 | 2.8.25 |
| symfony/security-core | packagist | v2.7.30, v2.7.31 | 2.7.32 |
| symfony/security-core | packagist | v3.2.10, v3.2.11 | 3.2.12 |
| symfony/security-core | packagist | v2.8.23, v2.8.24 | 2.8.25 |
| symfony/symfony | packagist | v3.3.3, v3.3.4 | 3.3.5 |
| symfony/symfony | packagist | v2.7.30, v2.7.31 | 2.7.32 |
| symfony/security | packagist | v3.3.3, v3.3.4 | 3.3.5 |
Vulnerability Classification
Common Weakness Enumeration (CWE) identifiers for this vulnerability type.
- CWE-284
CVSS Score Breakdown
What the CVSS (Common Vulnerability Scoring System) 9.8 score means for each attack dimension.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References
- https://nvd.nist.gov/vuln/detail/CVE-2017-11365ADVISORY
- https://github.com/symfony/symfony/pull/23507WEB
- https://github.com/symfony/symfony/commit/878198cefae028386c6dc800ccbf18f2b9cbff3fWEB
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/security-core/CVE-2017-11365.yamlWEB
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/security/CVE-2017-11365.yamlWEB
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2017-11365.yamlWEB
- https://github.com/symfony/symfonyPACKAGE
- https://symfony.com/blog/cve-2017-11365-empty-passwords-validation-issueWEB
- https://symfony.com/cve-2017-11365WEB
Frequently Asked Questions
- What is CVE-2017-11365?
- Symfony Incorrect Access Control This vulnerability has been assigned a severity rating of CRITICAL (CVSS score: 9.8/10).
- How do I check if my project is affected by CVE-2017-11365?
- CVE-2017-11365 affects symfony/security, symfony/symfony and symfony/security-core. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2017-11365 and 200,000+ other known vulnerabilities.
Severity & Exploitability
Exploitation is straightforward and causes maximum impact. Patch immediately.
Also Known As
Related CVEs
- CVE-2018-11407CRITICAL
Symfony Authentication Bypass
- CVE-2019-10910CRITICAL
Symfony Service IDs Allow Injection
- CVE-2016-2403CRITICAL
Symfony Authentication Bypass
- CVE-2018-11406HIGH
Symfony CSRF Token Fixation
- CVE-2026-45077HIGH
Symfony has Unauthenticated PHP Object Deserialization in MonologBridge server:log Listener
- CVE-2026-45063HIGH
Symfony Vulnerable to Identity Spoofing via Unanchored DN Regex in X509Authenticator
- CVE-2024-51736HIGH
Symfony vulnerable to command execution hijack on Windows with Process class
- CVE-2026-48784MEDIUM
Symfony: UrlGenerator Dot-Segment Encoding Skips Every Other Chained `../` or `./` → Generated URL Collapses Off-Route Under RFC 3986 Normalization
Check if you're affected
Scan your dependencies to see if this vulnerability affects your projects.
Scan Your Dependencies