CVE-2014-6393

moderate-risk

Published 2017-08-09

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.

Do I need to act?

0.29% chance of exploitation

EPSS score — low exploit probability

Not on CISA KEV list

No confirmed active exploitation reported to CISA

Patch status unknown

Check vendor advisories for fix availability and mitigation guidance

CVSS 6.1/10 Medium

NETWORK / LOW complexity

Affected Products (15)

Express

Affected Vendors

Openjsf

References (4)

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

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

/ 100

moderate-risk

Severity 23/34 · High

Exploitability 1/34 · Minimal

Exposure 18/34 · Moderate