2017-10-16 12:31:07 -04:00
{
2019-03-17 22:25:49 +00:00
"CVE_data_meta" : {
"ASSIGNER" : "cve@mitre.org" ,
"ID" : "CVE-2014-6393" ,
"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" : [
2017-10-16 12:31:07 -04:00
{
2019-03-17 22:25:49 +00:00
"lang" : "eng" ,
"value" : "The Express web framework before 3.11 and 4.x before 4.5 for Node.js does not provide a charset field in HTTP Content-Type headers in 400 level responses, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via characters in a non-standard encoding."
2017-10-16 12:31:07 -04:00
}
2019-03-17 22:25:49 +00:00
]
} ,
"problemtype" : {
"problemtype_data" : [
{
"description" : [
{
"lang" : "eng" ,
"value" : "n/a"
}
]
}
]
} ,
"references" : {
"reference_data" : [
{
"name" : "https://nodesecurity.io/advisories/express-no-charset-in-content-type-header" ,
"refsource" : "CONFIRM" ,
"url" : "https://nodesecurity.io/advisories/express-no-charset-in-content-type-header"
} ,
{
"name" : "https://bugzilla.redhat.com/show_bug.cgi?id=1203190" ,
"refsource" : "CONFIRM" ,
"url" : "https://bugzilla.redhat.com/show_bug.cgi?id=1203190"
}
]
}
}