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 attackers to conduct cross-site scripting (XSS) attacks via characters in…
Does this matter?
Lower severity and a low EPSS score (1.14%). Track it; it rarely justifies an emergency change on its own.
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 3.0
- 6.1 MEDIUMCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
- EPSS
- 1.14% probability · 65th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-79
- Affected
- openjsf/express
- Source
- cve@mitre.org
References
- https://bugzilla.redhat.com/show_bug.cgi?id=1203190Issue Tracking, Third Party Advisory, VDB Entry
- https://nodesecurity.io/advisories/express-no-charset-in-content-type-headerThird Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1203190Issue Tracking, Third Party Advisory, VDB Entry
- https://nodesecurity.io/advisories/express-no-charset-in-content-type-headerThird Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.