CVE-2017-16653

Name: CVE-2017-16653
Creator: NVD / NIST
Published: 2018-08-06T21:29:00.283+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 1.47%

Last modified Jun 17, 2026

CVE-2017-16653 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.47% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability

1.47%

70.5th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Vendor	Product	Versions
Sensiolabs	Symfony	>= 2.7.0, <= 2.7.37
Sensiolabs	Symfony	>= 3.2.0, <= 3.2.13
Sensiolabs	Symfony	>= 3.3.0, <= 3.3.12
Sensiolabs	Symfony	>= 3.8.0, <= 3.8.30
Debian	Debian Linux	9.0

References

https://github.com/symfony/symfony/pull/24992Issue Tracking, Third Party Advisory
https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-httpsIssue Tracking, Third Party Advisory
https://www.debian.org/security/2018/dsa-4262Third Party Advisory
https://github.com/symfony/symfony/pull/24992Issue Tracking, Third Party Advisory
https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-httpsIssue Tracking, Third Party Advisory
https://www.debian.org/security/2018/dsa-4262Third Party Advisory

Timeline

Published: Aug 6, 2018
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-16653?

How severe is CVE-2017-16653?

Severity scoring for CVE-2017-16653 is pending analysis. The EPSS model estimates a 1.47% probability of exploitation in the next 30 days.

How do I fix CVE-2017-16653?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-16653?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST