CVE-2014-6393

Description

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.

Category

6.1
CVSS
Severity: Medium
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.29%
Third-Party Advisory redhat.com Third-Party Advisory nodesecurity.io
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
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 vdb entry third party advisory

Frequently Asked Questions

What is the severity of CVE-2014-6393?
CVE-2014-6393 has been scored as a medium severity vulnerability.
How to fix CVE-2014-6393?
To fix CVE-2014-6393, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2014-6393 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2014-6393 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.