CVE-2014-6393
Last modified
CVE-2014-6393 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.14% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Openjsf | Express | <= 3.10.5 |
| Openjsf | Express | 4.0.0 |
| Openjsf | Express | 4.1.0 |
| Openjsf | Express | 4.1.1 |
| Openjsf | Express | 4.1.2 |
| Openjsf | Express | 4.2.0 |
| Openjsf | Express | 4.3.0 |
| Openjsf | Express | 4.3.1 |
| Openjsf | Express | 4.3.2 |
| Openjsf | Express | 4.4.0 |
| Openjsf | Express | 4.4.1 |
| Openjsf | Express | 4.4.2 |
| Openjsf | Express | 4.4.3 |
| Openjsf | Express | 4.4.4 |
| Openjsf | Express | 4.4.5 |
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
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2014-6393?
How severe is CVE-2014-6393?
How do I fix CVE-2014-6393?
Are you affected by CVE-2014-6393?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
