First published: Wed Mar 18 2015(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/express | <3.11 | 3.11 |
redhat/express | <4.5 | 4.5 |
Node.js Express | <=3.10.5 | |
Node.js Express | =4.0.0 | |
Node.js Express | =4.1.0 | |
Node.js Express | =4.1.1 | |
Node.js Express | =4.1.2 | |
Node.js Express | =4.2.0 | |
Node.js Express | =4.3.0 | |
Node.js Express | =4.3.1 | |
Node.js Express | =4.3.2 | |
Node.js Express | =4.4.0 | |
Node.js Express | =4.4.1 | |
Node.js Express | =4.4.2 | |
Node.js Express | =4.4.3 | |
Node.js Express | =4.4.4 | |
Node.js Express | =4.4.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-6393 is considered a high severity vulnerability that may allow remote XSS attacks due to improper handling of the Content-Type header.
To fix CVE-2014-6393, upgrade the Express framework to version 3.11 or 4.5 or later.
CVE-2014-6393 affects Express versions prior to 3.11 and any version before 4.5.
Yes, CVE-2014-6393 can allow attackers to conduct XSS attacks through non-standard encoding if exploited.
Yes, CVE-2014-6393 specifically affects the Express web framework used in Node.js applications.