CVE-2017-16653 - CVE House
Back to Database
Status published Medium CVE-2017-16653

An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14,...

Vulnerability 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.

Impact Analysis

Refer to official advisory for detailed impact metrics.

Remediation

Ensure systems are updated to the latest vendor-supplied patch levels.

THREAT MONITOR

Am I Vulnerable?

Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2017-16653

Credits & Attribution

No credits recorded in the NVD database.

References

More from sensiolabs

View All →
CVE-2019-18889
An issue was discovered in Symfony 3.4.0 through 3.4.34, 4.2.0...
Critical 9.8
CVE-2019-18888
An issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0...
High 7.5
CVE-2019-18887
An issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0...
High 8.1
CVE-2019-18886
An issue was discovered in Symfony 4.2.0 to 4.2.11 and...
Medium 5.3
CVE-2019-11325
An issue was discovered in Symfony before 4.2.12 and 4.3.x...
Critical 9.8

Affected Vendor

Affected Software

symfony, debian linux
Vulnerable Versions:
2.7.0, 3.2.0, 3.3.0, 3.8.0, 9.0

Timeline

Official Publish: August 6th, 2018
Last Modified: August 5th, 2024
Added to House: July 20th, 2026

CVSS Vectors

V3: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Weaknesses (CWE)

No CWE data available

MITRE ATT&CK TTPs

No associated TTPs found for this vulnerability.