This page was not yet optimized for use on mobile devices.
CVE-2020-15242
Data ?
Vulnerability ID | CVE-2020-15242 |
---|---|
Published on | 08.10.2020 20:15 |
Severity | MEDIUM |
Vulnerable configurations ?
-
cpe:2.3:a:vercel:next.js:9.5.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.1:-:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.1:canary0:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.1:canary1:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.1:canary2:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.1:canary3:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.2:-:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.2:canary0:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.2:canary1:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.2:canary10:*:*:*:node.js:*:*,
…
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.