Authentication Bypass in symfony/security-http (CVE-2021-32693)
Summary
Authentication bypass in symfony/security-http (CVE-2021-32693). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 5.3.2 or later.
Original description
The description as published by the source.
Symfony is a PHP framework for web and console applications and a set of reusable PHP components. A vulnerability related to firewall authentication is in Symfony starting with version 5.3.0 and prior to 5.3.2. When an application defines multiple firewalls, the token authenticated by one of the firewalls was available for all other firewalls. This could be abused when the application defines different providers for each part of the application, in such a situation, a user authenticated on a part of the application could be considered authenticated on the rest of the application. Starting in version 5.3.2, a patch ensures that the authenticated token is only available for the firewall that generates it.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-32693 has been found in symfony/security-http.
Successful exploitation can lead to full system takeover.
What to do: upgrade symfony/security-http to 5.3.2 or later.
If unsure, ask your IT team or search "symfony/security-http CVE-2021-32693" on the vendor's site.
CVE-2021-32693 (symfony/security-http) — CWE-287
Attack vector: remote (network-reachable) / no user interaction
Patched: 5.3.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in symfony/security-http.
Check the vendor advisory for the affected versions of symfony/security-http.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 5.3.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'symfony/security-http' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'symfony/security-http' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
symfony/security-httpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade symfony/security-http to 5.3.2ステージング環境で 5.3.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- patch github.com
- patch symfony.com
- web github.com
- web github.com
- web symfony.com