This page was not yet optimized for use on mobile devices.
CVE-2019-5739
Data ?
Vulnerability ID | CVE-2019-5739 |
---|---|
Published on | 28.03.2019 17:29 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:nodejs:node.js:4.2.0:*:*:*:lts:*:*:*,
cpe:2.3:a:nodejs:node.js:4.2.1:*:*:*:lts:*:*:*,
cpe:2.3:a:nodejs:node.js:4.2.2:*:*:*:lts:*:*:*,
cpe:2.3:a:nodejs:node.js:4.2.2:rc1:*:*:lts:*:*:*,
cpe:2.3:a:nodejs:node.js:4.2.2:rc2:*:*:lts:*:*:*,
cpe:2.3:a:nodejs:node.js:4.2.3:*:*:*:lts:*:*:*,
cpe:2.3:a:nodejs:node.js:4.2.4:*:*:*:lts:*:*:*,
cpe:2.3:a:nodejs:node.js:4.2.4:rc1:*:*:lts:*:*:*,
cpe:2.3:a:nodejs:node.js:4.2.5:*:*:*:lts:*:*:*,
cpe:2.3:a:nodejs:node.js:4.2.6:*:*:*:lts:*:*:*,
…
Vulnerable certificates ?
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.