This page was not yet optimized for use on mobile devices.
CVE-2024-34351
Data
| Vulnerability ID | CVE-2024-34351 |
|---|---|
| Published on | 14.05.2024 15:38 |
| Severity | HIGH |
Vulnerable configurations
-
cpe:2.3:a:vercel:next.js:13.4.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.4.1:-:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.4.1:canary0:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.4.1:canary1:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.4.1:canary2:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.4.2:-:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.4.2:canary0:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.4.2:canary1:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.4.2:canary2:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.4.2:canary3:*:*:*: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.