CVE-2017-16653: CSRF protection does not use different tokens for HTTP and HTTPS

Published Nov 16, 2017
·
Updated

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.

Other sources

CVE-2017-16653: CSRF protection does not use different tokens for HTTP and HTTPS

Affected Software

39 affected componentsFixes available
composer/symfony/symfony>=2.7.0, <2.7.38, >=2.8.0, <2.8.31, >=3.0.0, <3.1.0, >=3.1.0, <3.2.0, >=3.2.0, <3.2.14, >=3.3.0, <3.3.13
composer/symfony/security-csrf>=2.7.0, <2.7.38, >=2.8.0, <2.8.31, >=3.0.0, <3.1.0, >=3.1.0, <3.2.0, >=3.2.0, <3.2.14, >=3.3.0, <3.3.13
composer/symfony/security>=2.7.0, <2.7.38, >=2.8.0, <2.8.31, >=3.0.0, <3.1.0, >=3.1.0, <3.2.0, >=3.2.0, <3.2.14, >=3.3.0, <3.3.13
debian/symfony
3.4.22+dfsg-2+deb10u13.4.22+dfsg-2+deb10u24.4.19+dfsg-2+deb11u35.4.23+dfsg-15.4.29+dfsg-15.4.30+dfsg-1
composer/symfony/symfony>=3.3.0<3.3.13
3.3.13
composer/symfony/symfony>=3.0.0<3.2.14
3.2.14
composer/symfony/symfony>=2.8.0<2.8.31
2.8.31
composer/symfony/symfony>=2.7.0<2.7.38
2.7.38
composer/symfony/security>=3.3.0<3.3.13
3.3.13
composer/symfony/security>=3.0.0<3.2.14
3.2.14
composer/symfony/security>=2.8.0<2.8.31
2.8.31
composer/symfony/security>=2.7.0<2.7.38
2.7.38
composer/symfony/security-csrf>=3.3.0<3.3.13
3.3.13
composer/symfony/security-csrf>=3.0.0<3.2.14
3.2.14
composer/symfony/security-csrf>=2.8.0<2.8.31
2.8.31
composer/symfony/security-csrf>=2.7.0<2.7.38
2.7.38
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
composer/symfony/symfony>=2.7.0, <2.7.38
2.7.38
composer/symfony/symfony>=2.8.0, <2.8.31
2.8.31
composer/symfony/symfony>=3.0.0, <3.1.0
composer/symfony/symfony>=3.1.0, <3.2.0
composer/symfony/symfony>=3.2.0, <3.2.14
3.2.14
composer/symfony/symfony>=3.3.0, <3.3.13
3.3.13
composer/symfony/security>=2.7.0, <2.7.38
2.7.38
composer/symfony/security>=2.8.0, <2.8.31
2.8.31
composer/symfony/security>=3.0.0, <3.1.0
composer/symfony/security>=3.1.0, <3.2.0
composer/symfony/security>=3.2.0, <3.2.14
3.2.14
composer/symfony/security>=3.3.0, <3.3.13
3.3.13
composer/symfony/security-csrf>=2.7.0, <2.7.38
2.7.38
composer/symfony/security-csrf>=2.8.0, <2.8.31
2.8.31
composer/symfony/security-csrf>=3.0.0, <3.1.0
composer/symfony/security-csrf>=3.1.0, <3.2.0
composer/symfony/security-csrf>=3.2.0, <3.2.14
3.2.14
composer/symfony/security-csrf>=3.3.0, <3.3.13
3.3.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/symfony to a version that resolves this vulnerability.

    Fixed in 3.4.22+dfsg-2+deb10u1Fixed in 3.4.22+dfsg-2+deb10u2Fixed in 4.4.19+dfsg-2+deb11u3Fixed in 5.4.23+dfsg-1Fixed in 5.4.29+dfsg-1Fixed in 5.4.30+dfsg-1
  2. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 3.3.13
  3. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 3.2.14
  4. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 2.8.31
  5. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 2.7.38
  6. Upgrade

    Upgrade composer/symfony/security to a version that resolves this vulnerability.

    Fixed in 3.3.13
  7. Upgrade

    Upgrade composer/symfony/security to a version that resolves this vulnerability.

    Fixed in 3.2.14
  8. Upgrade

    Upgrade composer/symfony/security to a version that resolves this vulnerability.

    Fixed in 2.8.31
  9. Upgrade

    Upgrade composer/symfony/security to a version that resolves this vulnerability.

    Fixed in 2.7.38
  10. Upgrade

    Upgrade composer/symfony/security-csrf to a version that resolves this vulnerability.

    Fixed in 3.3.13
  11. Upgrade

    Upgrade composer/symfony/security-csrf to a version that resolves this vulnerability.

    Fixed in 3.2.14
  12. Upgrade

    Upgrade composer/symfony/security-csrf to a version that resolves this vulnerability.

    Fixed in 2.8.31
  13. Upgrade

    Upgrade composer/symfony/security-csrf to a version that resolves this vulnerability.

    Fixed in 2.7.38
  14. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.7.38
  15. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.8.31
  16. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.2.14
  17. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.3.13
  18. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.4-BETA5
  19. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.0-BETA5

Event History

Nov 16, 2017
Advisory Published
via Packagist·03:12 PM
Data Sourced
via Packagist·03:12 PM
DescriptionSeverityAffected Software
Advisory Published
03:24 PM
Aug 6, 2018
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description

Frequently Asked Questions

1

What is the CVE ID for this vulnerability?

The CVE ID for this vulnerability is CVE-2017-16653.

2

What is the severity level of CVE-2017-16653?

The severity level of CVE-2017-16653 is medium, with a severity value of 5.9.

3

Which versions of Symfony are affected by CVE-2017-16653?

Versions before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5 of Symfony are affected by CVE-2017-16653.

4

How can this vulnerability be exploited?

This vulnerability can be exploited through a MITM (Man-in-the-Middle) attack on HTTP to obtain the CSRF token and use it in HTTPS.

5

Where can I find more information about CVE-2017-16653?

You can find more information about CVE-2017-16653 on the Symfony website, the NIST NVD website, and the GitHub pull request.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203