For your digest
turbo_boost-commands, @turbo-boost/commands: TurboBoost Commands vulnerable to arbitrary method invocation
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- turbo_boost-commands (RubyGems): every version, before 0.1.3
- turbo_boost-commands (RubyGems): from 0.2.0, before 0.2.2
- @turbo-boost/commands (npm): every version, before 0.1.3
- @turbo-boost/commands (npm): from 0.2.0, before 0.2.2
The fix
turbo_boost-commands (RubyGems) fixed in 0.1.3
bundlerbundle update --conservative turbo_boost-commandsCheck what is installedbundle info turbo_boost-commandsPaste into Cursor, Lovable or Claude CodeUpgrade the RubyGems dependency turbo_boost-commands to 0.1.3 or the nearest later release, to fix CVE-2024-28181. 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.turbo_boost-commands (RubyGems) fixed in 0.2.2
bundlerbundle update --conservative turbo_boost-commandsCheck what is installedbundle info turbo_boost-commandsPaste into Cursor, Lovable or Claude CodeUpgrade the RubyGems dependency turbo_boost-commands to 0.2.2 or the nearest later release, to fix CVE-2024-28181. 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.@turbo-boost/commands (npm) fixed in 0.1.3
npmnpm install "@turbo-boost/commands@0.1.3"pnpmpnpm add "@turbo-boost/commands@0.1.3"yarnyarn add "@turbo-boost/commands@0.1.3"bunbun add "@turbo-boost/commands@0.1.3"Check what is installednpm ls @turbo-boost/commandsPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @turbo-boost/commands to 0.1.3 or the nearest later release, to fix CVE-2024-28181. 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.@turbo-boost/commands (npm) fixed in 0.2.2
npmnpm install "@turbo-boost/commands@0.2.2"pnpmpnpm add "@turbo-boost/commands@0.2.2"yarnyarn add "@turbo-boost/commands@0.2.2"bunbun add "@turbo-boost/commands@0.2.2"Check what is installednpm ls @turbo-boost/commandsPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @turbo-boost/commands to 0.2.2 or the nearest later release, to fix CVE-2024-28181. 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".