CVE-2014-6393

medium
Published 2017-08-09 ยท Modified 2023-11-08
CVSS v3
6.1
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
6.1

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.

Predictions

Exploit likelihood
71%
Patch ETA
โ€”

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ€” if you've already worked around this in production โ€” publish your fix to the community-verified tier.

โœš Propose a mitigation on Community โ†’ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

debian Debian Fixed 5 releases
VersionStatusFixed in
trixie Fixed 4.16.4-1
sid Fixed 4.16.4-1
forky Fixed 4.16.4-1
bullseye Fixed 4.16.4-1
bookworm Fixed 4.16.4-1

Package impact

EcosystemPackageVulnerableFixed
npm npmexpress<3.11.03.11.0
npm npmexpress>=4.0.0,<4.5.04.5.0

Application impact

VendorProductVersionsFixed
openjsfexpress4.3.0
openjsfexpress4.3.1
openjsfexpress4.3.2
openjsfexpress{"endIncluding":"3.10.5"}
openjsfexpress4.0.0
openjsfexpress4.1.0
openjsfexpress4.1.1
openjsfexpress4.1.2
openjsfexpress4.2.0
openjsfexpress4.4.0
openjsfexpress4.4.1
openjsfexpress4.4.2
openjsfexpress4.4.3
openjsfexpress4.4.4
openjsfexpress4.4.5

References

CWEs

CWE-79

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.