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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2018-0603 | 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. |
Github GHSA |
GHSA-gpvr-g6gh-9mc2 | No Charset in Content-Type Header in express |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-06T12:17:23.956Z
Reserved: 2014-09-15T00:00:00
Link: CVE-2014-6393
No data.
Status : Deferred
Published: 2017-08-09T18:29:00.480
Modified: 2025-04-20T01:37:25.860
Link: CVE-2014-6393
OpenCVE Enrichment
No data.
EUVD
Github GHSA