CVE-2014-6393 No Charset in Content-Type Header in express
MediumCVSS 6.1
EPSS 1.1%
- Published
- Updated
- Exploit status
- No public exploit known
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.
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| npm express(npm) | < 3.11.0 | 3.11.0 |
| npm express(npm) | >= 4.0.0, < 4.5.0 | 4.5.0 |
| debian/node-express(Debian:12) | < 4.16.4-1 | 4.16.4-1 |
| debian/node-express(Debian:13) | < 4.16.4-1 | 4.16.4-1 |
| debian/node-express(Debian:14) | < 4.16.4-1 | 4.16.4-1 |
| openjsf express | <= 3.10.5 | No fix listed |
| openjsf express | = 4.0.0 | No fix listed |
| openjsf express | = 4.1.0 | No fix listed |
| openjsf express | = 4.1.1 | No fix listed |
| openjsf express | = 4.1.2 | No fix listed |
| openjsf express | = 4.2.0 | No fix listed |
| openjsf express | = 4.3.0 | No fix listed |
| openjsf express | = 4.3.1 | No fix listed |
| openjsf express | = 4.3.2 | No fix listed |
| openjsf express | = 4.4.0 | No fix listed |
| openjsf express | = 4.4.1 | No fix listed |
| openjsf express | = 4.4.2 | No fix listed |
| openjsf express | = 4.4.3 | No fix listed |
| openjsf express | = 4.4.4 | No fix listed |
| openjsf express | = 4.4.5 | No fix listed |
References
- nvd.nist.gov third-party-advisory
- github.com
- www.npmjs.com
- bugzilla.redhat.com issue-tracking third-party-advisory vdb-entry
- Debian Security Tracker CVE-2014-6393 vendor-advisory
- nodesecurity.io third-party-advisory