This weekExploitable · Confirmed
vite: Vite's `server.fs.deny` is bypassed when using `?import&raw`
There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.
Does it affect what I run?
vite (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- vite (npm): from 5.4.0, before 5.4.6
- vite (npm): from 5.3.0, before 5.3.6
- vite (npm): from 5.2.0, before 5.2.14
- vite (npm): from 4.0.0, before 4.5.4
- vite (npm): every version, before 3.2.11
- vite (npm): from 5.0.0, before 5.1.8
The fix
vite (npm) fixed in 5.4.6
npmnpm install vite@5.4.6pnpmpnpm add vite@5.4.6yarnyarn add vite@5.4.6bunbun add vite@5.4.6Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 5.4.6 or the nearest later release, to fix CVE-2024-45811. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vite (npm) fixed in 5.3.6
npmnpm install vite@5.3.6pnpmpnpm add vite@5.3.6yarnyarn add vite@5.3.6bunbun add vite@5.3.6Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 5.3.6 or the nearest later release, to fix CVE-2024-45811. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vite (npm) fixed in 5.2.14
npmnpm install vite@5.2.14pnpmpnpm add vite@5.2.14yarnyarn add vite@5.2.14bunbun add vite@5.2.14Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 5.2.14 or the nearest later release, to fix CVE-2024-45811. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vite (npm) fixed in 4.5.4
npmnpm install vite@4.5.4pnpmpnpm add vite@4.5.4yarnyarn add vite@4.5.4bunbun add vite@4.5.4Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 4.5.4 or the nearest later release, to fix CVE-2024-45811. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vite (npm) fixed in 3.2.11
npmnpm install vite@3.2.11pnpmpnpm add vite@3.2.11yarnyarn add vite@3.2.11bunbun add vite@3.2.11Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 3.2.11 or the nearest later release, to fix CVE-2024-45811. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vite (npm) fixed in 5.1.8
npmnpm install vite@5.1.8pnpmpnpm add vite@5.1.8yarnyarn add vite@5.1.8bunbun add vite@5.1.8Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 5.1.8 or the nearest later release, to fix CVE-2024-45811. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
Exploitable · Confirmed
CISA's assessment in the CVE record says a proof of concept is public.
CISA Vulnrichment (SSVC and KEV fields inside CVE records)Stated
Timeline
- First published here, as "For your digest".
- Level changed from "For your digest" to "This week".
- Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))