# CVE-2017-11365: Symfony Incorrect Access Control > Remote attackers can bypass access controls in the Symfony password validator component due to incorrect access control implementation. - **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 May 2019 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-q87v-q8fw-gmj5 ## What is CVE-2017-11365? CVE-2017-11365 is a critical missing authorization vulnerability in Sensiolabs Symfony, published on 23 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Certain Symfony products are affected by: Incorrect Access Control. This affects Symfony 2.7.30 and Symfony 2.8.23 and Symfony 3.2.10 and Symfony 3.3.3. The type of exploitation is: remote. The component is: Password validator. Weakness: CWE-284 (Improper Access Control) ## Which versions are affected by CVE-2017-11365? 24 open source packages ship an affected version, including symfony/security, symfony/security-core and symfony/symfony. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `symfony/security` | Packagist | From 2.7.30 | 2.7.32 | | `symfony/security` | Packagist | From 2.7.30 | 2.7.32 | | `symfony/security` | Packagist | From 2.8.23 | 2.8.25 | | `symfony/security` | Packagist | From 2.8.23 | 2.8.25 | | `symfony/security` | Packagist | From 3.2.10 | 3.2.12 | | `symfony/security` | Packagist | From 3.2.10 | 3.2.12 | | `symfony/security` | Packagist | From 3.3.3 | 3.3.5 | | `symfony/security` | Packagist | From 3.3.3 | 3.3.5 | | `symfony/security-core` | Packagist | From 2.7.30 | 2.7.32 | | `symfony/security-core` | Packagist | From 2.7.30 | 2.7.32 | | `symfony/security-core` | Packagist | From 2.8.23 | 2.8.25 | | `symfony/security-core` | Packagist | From 2.8.23 | 2.8.25 | | `symfony/security-core` | Packagist | From 3.2.10 | 3.2.12 | | `symfony/security-core` | Packagist | From 3.2.10 | 3.2.12 | | `symfony/security-core` | Packagist | From 3.3.3 | 3.3.5 | | `symfony/security-core` | Packagist | From 3.3.3 | 3.3.5 | | `symfony/symfony` | Packagist | From 2.7.30 | 2.7.32 | | `symfony/symfony` | Packagist | From 2.7.30 | 2.7.32 | | `symfony/symfony` | Packagist | From 2.8.23 | 2.8.25 | | `symfony/symfony` | Packagist | From 2.8.23 | 2.8.25 | | `symfony/symfony` | Packagist | From 3.2.10 | 3.2.12 | | `symfony/symfony` | Packagist | From 3.2.10 | 3.2.12 | | `symfony/symfony` | Packagist | From 3.3.3 | 3.3.5 | | `symfony/symfony` | Packagist | From 3.3.3 | 3.3.5 | Products: Sensiolabs Symfony. ## How do I fix CVE-2017-11365? Upgrade symfony/security to a fixed version for your release line: 2.7.32, 2.8.25, 3.2.12 or 3.3.5. ## Is CVE-2017-11365 being exploited? There is no known exploitation of CVE-2017-11365 in the wild and no public exploit code. ## Other vulnerabilities in Sensiolabs Symfony - [CVE-2019-11325](https://insights.sbomify.com/CVE-2019-11325/): Improper Input Validation in Symfony (critical 9.8) - [CVE-2019-10913](https://insights.sbomify.com/CVE-2019-10913/): Invalid HTTP method overrides allow possible XSS or other attacks in Symfony (critical 9.8) - [CVE-2018-11407](https://insights.sbomify.com/CVE-2018-11407/): Symfony Authentication Bypass (critical 9.8) - [CVE-2016-2403](https://insights.sbomify.com/CVE-2016-2403/): Symfony Authentication Bypass (critical 9.8) - [CVE-2026-45063](https://insights.sbomify.com/CVE-2026-45063/): Symfony: Identity Spoofing via Unanchored DN Regex in X509Authenticator (critical 9.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-11365 and fix it if it is affected. What it is: CVE-2017-11365 is a critical missing authorization vulnerability in Sensiolabs Symfony, published on 23 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2017-11365 in the wild and no public exploit code. Affected packages and fixed versions: - symfony/security (Packagist): affected from 2.7.30; fixed in 2.7.32 - symfony/security (Packagist): affected from 2.7.30; fixed in 2.7.32 - symfony/security (Packagist): affected from 2.8.23; fixed in 2.8.25 - symfony/security (Packagist): affected from 2.8.23; fixed in 2.8.25 - symfony/security (Packagist): affected from 3.2.10; fixed in 3.2.12 - symfony/security (Packagist): affected from 3.2.10; fixed in 3.2.12 - symfony/security (Packagist): affected from 3.3.3; fixed in 3.3.5 - symfony/security (Packagist): affected from 3.3.3; fixed in 3.3.5 - symfony/security-core (Packagist): affected from 2.7.30; fixed in 2.7.32 - symfony/security-core (Packagist): affected from 2.7.30; fixed in 2.7.32 - symfony/security-core (Packagist): affected from 2.8.23; fixed in 2.8.25 - symfony/security-core (Packagist): affected from 2.8.23; fixed in 2.8.25 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2017-11365/ (Markdown: https://insights.sbomify.com/CVE-2017-11365/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-11365 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-11365 - OSV: https://osv.dev/vulnerability/CVE-2017-11365 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-11365/ Summaries are generated and may contain mistakes; the official description above is the record.