Medium severity · published Aug 9, 2017
CVE-2014-6393
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…
6.1
CVSS
1.1%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Confidentiality
Low
Integrity
Low
Availability
None
Scope
Changed
Exploitation
Is it being used?
Exploit prediction (EPSS)1.1% · higher than 67% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
EX
Express · Openjsf
through 3.10.5; 4.0.0; 4.1.0; 4.1.1; 4.1.2; 4.2.0; +9 more · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2014-6393
CVE.org
https://www.cve.org/CVERecord?id=CVE-2014-6393
Issue Tracking
https://bugzilla.redhat.com/show_bug.cgi?id=1203190
Third Party Advisory
https://nodesecurity.io/advisories/express-no-charset-in-content-type-header
More from Express
7.5
CVE-2022-24999
qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be…
6.1
CVE-2024-29041
Express.js minimalist web framework for node
5.3
CVE-2024-10491
Preload arbitrary resources by injecting additional `Link` headers
4.7
CVE-2024-43796
express vulnerable to XSS via response.redirect()