CVE-2017-16653
Description
An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Debian Fixed 5 releases
| Version | Status | Fixed in |
|---|---|---|
| trixie | Fixed | 3.4.0+dfsg-1 |
| sid | Fixed | 3.4.0+dfsg-1 |
| forky | Fixed | 3.4.0+dfsg-1 |
| bullseye | Fixed | 3.4.0+dfsg-1 |
| bookworm | Fixed | 3.4.0+dfsg-1 |
Package impact
| Ecosystem | Package | Vulnerable | Fixed |
|---|---|---|---|
| Packagist | symfony/security-csrf | >=2.7.0,<2.7.38 | 2.7.38 |
| Packagist | symfony/security-csrf | >=2.8.0,<2.8.31 | 2.8.31 |
| Packagist | symfony/security-csrf | >=3.0.0,<3.2.14 | 3.2.14 |
| Packagist | symfony/security-csrf | >=3.3.0,<3.3.13 | 3.3.13 |
| Packagist | symfony/security | >=2.7.0,<2.7.38 | 2.7.38 |
| Packagist | symfony/security | >=2.8.0,<2.8.31 | 2.8.31 |
| Packagist | symfony/security | >=3.0.0,<3.2.14 | 3.2.14 |
| Packagist | symfony/security | >=3.3.0,<3.3.13 | 3.3.13 |
| Packagist | symfony/symfony | >=2.7.0,<2.7.38 | 2.7.38 |
| Packagist | symfony/symfony | >=2.8.0,<2.8.31 | 2.8.31 |
| Packagist | symfony/symfony | >=3.0.0,<3.2.14 | 3.2.14 |
| Packagist | symfony/symfony | >=3.3.0,<3.3.13 | 3.3.13 |
References
- https://nvd.nist.gov/vuln/detail/CVE-2017-16653
- https://github.com/symfony/symfony/pull/24992
- https://github.com/symfony/symfony/commit/b4dbdd7cd8732483d585eacff3428c16b07ad15e
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/security-csrf/CVE-2017-16653.yaml
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/security/CVE-2017-16653.yaml
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2017-16653.yaml
- https://github.com/symfony/symfony
- https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https
- https://symfony.com/cve-2017-16653
- https://www.debian.org/security/2018/dsa-4262
- https://security-tracker.debian.org/tracker/CVE-2017-16653
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.