CVE-2017-16653

Published Aug 6, 2018 CVSS 3.0 · 5.9 Medium EPSS 1.5% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DSA Debian DSA DSA-4262-1 symfony security update
EUVD EUVD EUVD-2022-3279 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.
Github GHSA Github GHSA GHSA-92x6-h2gr-8gxq Symfony CSRF Vulnerability
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Aug 5, 2024, 8:27 PM
Reserved
Nov 7, 2017, 12:00 AM
Status
Modified
Published
Aug 6, 2018, 9:29 PM
Modified
Jun 17, 2026, 1:09 AM