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 |
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 |
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 02:14
Type | Values Removed | Values Added |
---|---|---|
References | () https://bugzilla.redhat.com/show_bug.cgi?id=1203190 - Issue Tracking, Third Party Advisory, VDB Entry | |
References | () https://nodesecurity.io/advisories/express-no-charset-in-content-type-header - Third Party Advisory |
Information
Published : 2017-08-09 18:29
Updated : 2024-11-21 02:14
NVD link : CVE-2014-6393
Mitre link : CVE-2014-6393
CVE.ORG link : CVE-2014-6393
JSON object : View
Products Affected
openjsf
- express
CWE
CWE-79
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')