Lucene search
K

No Charset in Content-Type Header

🗓️ 17 Oct 2015 19:41:46Reported by Paweł HałdrzyńskiType 
nodejs
 nodejs
🔗 www.npmjs.com👁 37 Views

Vulnerable express does not specify charset in content-type header for 400 level responses, allowing potential XSS attacks using UTF-7

Related
Detection
ReporterTitlePublishedViews
Family
CNVD
Joyent Node.js Express web framework cross-site scripting vulnerability
17 Aug 201700:00
cnvd
CVE
CVE-2014-6393
9 Aug 201718:00
cve
Cvelist
CVE-2014-6393
9 Aug 201718:00
cvelist
Debian CVE
CVE-2014-6393
9 Aug 201718:00
debiancve
EUVD
EUVD-2018-0603
7 Oct 202500:30
euvd
Github Security Blog
No Charset in Content-Type Header in express
23 Oct 201817:22
github
NVD
CVE-2014-6393
9 Aug 201718:29
nvd
OSV
DEBIAN-CVE-2014-6393
9 Aug 201718:29
osv
OSV
GHSA-GPVR-G6GH-9MC2 No Charset in Content-Type Header in express
23 Oct 201817:22
osv
OSV
UBUNTU-CVE-2014-6393
9 Aug 201718:29
osv
Rows per page
Vulners
Node
expressRange<3.11
OR
expressRange44.5

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation

23 Sep 2021 08:03Current
1.6Low risk
Vulners AI Score1.6
EPSS0.0029
37