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.
References
Link | Resource |
---|---|
https://bugzilla.redhat.com/show_bug.cgi?id=1203190 | Issue Tracking Third Party Advisory VDB Entry |
https://nodesecurity.io/advisories/express-no-charset-in-content-type-header | Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2017-08-09T18:00:00
Updated: 2017-08-09T17:57:01
Reserved: 2014-09-15T00:00:00
Link: CVE-2014-6393
JSON object: View
NVD Information
Status : Analyzed
Published: 2017-08-09T18:29:00.480
Modified: 2021-07-30T16:36:04.447
Link: CVE-2014-6393
JSON object: View
Redhat Information
No data.
CWE