CVE-2017-16653
Published: 6 August 2018
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.
Priority
Status
Package | Release | Status |
---|---|---|
symfony Launchpad, Ubuntu, Debian |
bionic |
Not vulnerable
(3.4.6+dfsg-1)
|
cosmic |
Not vulnerable
(3.4.15+dfsg-2ubuntu4)
|
|
disco |
Not vulnerable
(3.4.15+dfsg-2ubuntu4)
|
|
eoan |
Not vulnerable
(3.4.15+dfsg-2ubuntu4)
|
|
focal |
Not vulnerable
(3.4.15+dfsg-2ubuntu4)
|
|
groovy |
Not vulnerable
(3.4.15+dfsg-2ubuntu4)
|
|
hirsute |
Not vulnerable
(3.4.15+dfsg-2ubuntu4)
|
|
impish |
Not vulnerable
(3.4.15+dfsg-2ubuntu4)
|
|
jammy |
Not vulnerable
(3.4.15+dfsg-2ubuntu4)
|
|
kinetic |
Not vulnerable
(3.4.15+dfsg-2ubuntu4)
|
|
lunar |
Not vulnerable
(3.4.15+dfsg-2ubuntu4)
|
|
mantic |
Not vulnerable
(3.4.15+dfsg-2ubuntu4)
|
|
noble |
Not vulnerable
(3.4.15+dfsg-2ubuntu4)
|
|
trusty |
Does not exist
|
|
upstream |
Released
(3.4.0+dfsg-1)
|
|
xenial |
Needed
|
Severity score breakdown
Parameter | Value |
---|---|
Base score | 5.9 |
Attack vector | Network |
Attack complexity | High |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | High |
Integrity impact | None |
Availability impact | None |
Vector | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |