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.

5.9

CVSS

Severity: Medium

CVSS 3.0 •

CVSS 2.0 •

EPSS 0.36%

Vendor Advisory debian.org

Affected: n/a n/a

References

Link	Tags
https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https	issue tracking third party advisory
https://github.com/symfony/symfony/pull/24992	issue tracking third party advisory
https://www.debian.org/security/2018/dsa-4262	third party advisory vendor advisory

Frequently Asked Questions

What is the severity of CVE-2017-16653?: CVE-2017-16653 has been scored as a medium severity vulnerability.
How to fix CVE-2017-16653?: To fix CVE-2017-16653, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-16653 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2017-16653 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.