CVE-2017-16653GHSA-92X6-H2GR-8GXQ
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.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.7.38, 2.8.31, 3.2.14, 3.3.13
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- symfony/security-csrfPackagist
From 2.7.0 · fixed in 2.7.38
- symfony/security-csrfPackagist
From 2.8.0 · fixed in 2.8.31
- symfony/security-csrfPackagist
From 3.0.0 · fixed in 3.2.14
- symfony/security-csrfPackagist
From 3.3.0 · fixed in 3.3.13
- symfony/securityPackagist
From 2.7.0 · fixed in 2.7.38
- symfony/securityPackagist
From 2.8.0 · fixed in 2.8.31
- symfony/securityPackagist
From 3.0.0 · fixed in 3.2.14
- symfony/securityPackagist
From 3.3.0 · fixed in 3.3.13
- symfony/symfonyPackagist
From 2.7.0 · fixed in 2.7.38
- symfony/symfonyPackagist
From 2.8.0 · fixed in 2.8.31
- symfony/symfonyPackagist
From 3.0.0 · fixed in 3.2.14
- symfony/symfonyPackagist
From 3.3.0 · fixed in 3.3.13