2017-11-07 19:02:19 -05:00
{
2019-03-18 07:15:47 +00:00
"CVE_data_meta" : {
"ASSIGNER" : "cve@mitre.org" ,
"ID" : "CVE-2017-16653" ,
"STATE" : "PUBLIC"
} ,
"affects" : {
"vendor" : {
"vendor_data" : [
{
"product" : {
"product_data" : [
{
"product_name" : "n/a" ,
"version" : {
"version_data" : [
{
"version_value" : "n/a"
}
]
}
}
]
} ,
"vendor_name" : "n/a"
}
]
}
} ,
"data_format" : "MITRE" ,
"data_type" : "CVE" ,
"data_version" : "4.0" ,
"description" : {
"description_data" : [
2018-08-06 17:05:23 -04:00
{
2019-03-18 07:15:47 +00:00
"lang" : "eng" ,
"value" : "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."
2018-08-06 17:05:23 -04:00
}
2019-03-18 07:15:47 +00:00
]
} ,
"problemtype" : {
"problemtype_data" : [
{
"description" : [
{
"lang" : "eng" ,
"value" : "n/a"
}
]
}
]
} ,
"references" : {
"reference_data" : [
{
"name" : "https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https" ,
"refsource" : "CONFIRM" ,
"url" : "https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https"
} ,
{
"name" : "https://github.com/symfony/symfony/pull/24992" ,
"refsource" : "CONFIRM" ,
"url" : "https://github.com/symfony/symfony/pull/24992"
} ,
{
"name" : "DSA-4262" ,
"refsource" : "DEBIAN" ,
"url" : "https://www.debian.org/security/2018/dsa-4262"
}
]
}
}