First published: Wed Mar 18 2015(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/express | <3.11 | 3.11 |
redhat/express | <4.5 | 4.5 |
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.