For your digest
vite: Vite's `server.fs.deny` did not deny requests for patterns with directories.
It touches something Phylax follows. No evidence of use yet.
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 2.7.0, before 2.9.18
- vite (npm): from 3.0.0, before 3.2.10
- vite (npm): from 4.0.0, before 4.5.3
- vite (npm): from 5.0.0, before 5.0.13
- vite (npm): from 5.1.0, before 5.1.7
- vite (npm): from 5.2.0, before 5.2.6
The fix
vite (npm) fixed in 2.9.18
npmnpm install vite@2.9.18pnpmpnpm add vite@2.9.18yarnyarn add vite@2.9.18bunbun add vite@2.9.18Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 2.9.18 or the nearest later release, to fix CVE-2024-31207. 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.10
npmnpm install vite@3.2.10pnpmpnpm add vite@3.2.10yarnyarn add vite@3.2.10bunbun add vite@3.2.10Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 3.2.10 or the nearest later release, to fix CVE-2024-31207. 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.3
npmnpm install vite@4.5.3pnpmpnpm add vite@4.5.3yarnyarn add vite@4.5.3bunbun add vite@4.5.3Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 4.5.3 or the nearest later release, to fix CVE-2024-31207. 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.0.13
npmnpm install vite@5.0.13pnpmpnpm add vite@5.0.13yarnyarn add vite@5.0.13bunbun add vite@5.0.13Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 5.0.13 or the nearest later release, to fix CVE-2024-31207. 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.7
npmnpm install vite@5.1.7pnpmpnpm add vite@5.1.7yarnyarn add vite@5.1.7bunbun add vite@5.1.7Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 5.1.7 or the nearest later release, to fix CVE-2024-31207. 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.6
npmnpm install vite@5.2.6pnpmpnpm add vite@5.2.6yarnyarn add vite@5.2.6bunbun add vite@5.2.6Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 5.2.6 or the nearest later release, to fix CVE-2024-31207. 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
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".