Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2017-16653

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-06T21:29:00.283

Last Modified

2024-11-21T03:16:46.210

Status

Modified

Source

[email protected]

Severity

CVSSv3.0: 5.9 (MEDIUM)

CVSSv2 Vector

AV:N/AC:M/Au:N/C:P/I:N/A:N

Access Vector: NETWORK
Access Complexity: MEDIUM
Authentication: NONE
Confidentiality Impact: PARTIAL
Integrity Impact: NONE
Availability Impact: NONE

Exploitability Score

8.6

Impact Score

2.9

Weaknesses

Type: Primary
NVD-CWE-noinfo

Affected Vendors & Products

Type	Vendor	Product	Version/Range	Vulnerable?
Application	sensiolabs	symfony	≤ 2.7.37	Yes
Application	sensiolabs	symfony	≤ 3.2.13	Yes
Application	sensiolabs	symfony	≤ 3.3.12	Yes
Application	sensiolabs	symfony	≤ 3.8.30	Yes
Operating System	debian	debian_linux	9.0	Yes

References

https://github.com/symfony/symfony/pull/24992 Issue Tracking, Third Party Advisory ([email protected])
https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https Issue Tracking, Third Party Advisory ([email protected])
https://www.debian.org/security/2018/dsa-4262 Third Party Advisory ([email protected])
https://github.com/symfony/symfony/pull/24992 Issue Tracking, Third Party Advisory (af854a3a-2127-422b-91ae-364da2661108)
https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https Issue Tracking, Third Party Advisory (af854a3a-2127-422b-91ae-364da2661108)
https://www.debian.org/security/2018/dsa-4262 Third Party Advisory (af854a3a-2127-422b-91ae-364da2661108)