CVSS 3.0
7.5 highCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NHigh (7.5) in zeit next.js. EPSS 9.1% estimated probability of exploitation activity in the next 30 days. Fixed in next 4.2.3.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:Nnext (npm): fixed in 4.2.3Explain CVE-2018-6184 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2018-6184?via=ask-ai-copy and https://cve.bz/cve/CVE-2018-6184?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2018-6184 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| zeit:next.js | 4.0.0 |
| zeit:next.js | 4.0.1 |
| zeit:next.js | 4.0.2 |
| zeit:next.js | 4.0.3 |
| zeit:next.js | 4.0.4 |
| zeit:next.js | 4.0.5 |
| zeit:next.js | 4.1.0 |
| zeit:next.js | 4.1.1 |
| zeit:next.js | 4.1.2 |
| zeit:next.js | 4.1.3 |
| zeit:next.js | 4.1.4 |
| zeit:next.js | 4.1.4:canary_1 |
| zeit:next.js | 4.1.4:canary_2 |
| zeit:next.js | 4.2.0 |
| zeit:next.js | 4.2.0:canary_1 |
| zeit:next.js | 4.2.1 |
| zeit:next.js | 4.2.2 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-m34x-wgrh-g897 | npm | next | >=1.0.0 <4.2.3 | 4.2.3 |
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.