This page was not yet optimized for use on mobile devices.
CVE-2024-51479
Data
| Vulnerability ID | CVE-2024-51479 |
|---|---|
| Published on | 17.12.2024 19:15 |
| Severity | HIGH |
Vulnerable configurations
-
cpe:2.3:a:vercel:next.js:9.5.5:-:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.5:canary0:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.5:canary1:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.6:-:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.6:canary0:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.6:canary1:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.6:canary10:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.6:canary11:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.6:canary12:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:9.5.6:canary13:*:*:*: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.