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.
Published: 2018-08-06
Score: 5.9 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

No analysis available yet.

Remediation

No remediation available yet.

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.

Subscriptions

Debian Debian Linux
Sensiolabs Symfony
cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-05T20:27:04.403Z

Reserved: 2017-11-07T00:00:00.000Z

Link: CVE-2017-16653

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2018-08-06T21:29:00.283

Modified: 2024-11-21T03:16:46.210

Link: CVE-2017-16653

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses