CVE-2017-16653 Affecting symfony package, versions <3.4.0+dfsg-1
Threat Intelligence
Exploit maturity not defined.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIAN11-SYMFONY-523257
- published22 Jul 2018
- disclosed6 Aug 2018
Introduced: 22 Jul 2018
CVE-2017-16653 (opens in a new tab)How to fix?
Upgrade Debian:11 symfony to version 3.4.0+dfsg-1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream symfony package and not the symfony package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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.
References
- https://security-tracker.debian.org/tracker/CVE-2017-16653
- https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https
- https://www.debian.org/security/2018/dsa-4262
- https://github.com/symfony/symfony/pull/24992
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2017-16653