Vulnerability in Sensiolabs Symfony
CVE-2017-16653
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.9 (Medium). Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
EPSS: 0.015 (73.0th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 73rd percentile — 73.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.015 · newest: 0.015 · change: +0.000
Affected products
- Sensiolabs Symfony
- Debian Linux — versions 9.0
References
- symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-f… (Third Party Advisory, Issue Tracking)
- github.com/symfony/symfony/pull/24992 (Third Party Advisory, Issue Tracking)
- www.debian.org/security/2018/dsa-4262 (vendor-advisory, Third Party Advisory)
Frequently asked questions
- What is CVE-2017-16653?
- CVE-2017-16653 is a medium-severity vulnerability in Sensiolabs Symfony. CVSS score: 5.9/10. Published 2018-08-06.
- How severe is CVE-2017-16653?
- Medium severity. CVSS v3 base score is 5.9 out of 10.