For your digest
lodash, lodash-es: Prototype Pollution in lodash
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
- lodash (npm): every version, before 4.17.12
- lodash-es (npm): every version, before 4.17.14
- lodash-amd (npm): every version, before 4.17.13
- lodash.defaultsdeep (npm): every version, before 4.6.1
- lodash-rails (RubyGems): every version, before 4.17.12
The fix
lodash (npm) fixed in 4.17.12
npmnpm install lodash@4.17.12pnpmpnpm add lodash@4.17.12yarnyarn add lodash@4.17.12bunbun add lodash@4.17.12Check what is installednpm ls lodashPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency lodash to 4.17.12 or the nearest later release, to fix CVE-2019-10744. 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.lodash-es (npm) fixed in 4.17.14
npmnpm install lodash-es@4.17.14pnpmpnpm add lodash-es@4.17.14yarnyarn add lodash-es@4.17.14bunbun add lodash-es@4.17.14Check what is installednpm ls lodash-esPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency lodash-es to 4.17.14 or the nearest later release, to fix CVE-2019-10744. 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.lodash-amd (npm) fixed in 4.17.13
npmnpm install lodash-amd@4.17.13pnpmpnpm add lodash-amd@4.17.13yarnyarn add lodash-amd@4.17.13bunbun add lodash-amd@4.17.13Check what is installednpm ls lodash-amdPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency lodash-amd to 4.17.13 or the nearest later release, to fix CVE-2019-10744. 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.lodash.defaultsdeep (npm) fixed in 4.6.1
npmnpm install lodash.defaultsdeep@4.6.1pnpmpnpm add lodash.defaultsdeep@4.6.1yarnyarn add lodash.defaultsdeep@4.6.1bunbun add lodash.defaultsdeep@4.6.1Check what is installednpm ls lodash.defaultsdeepPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency lodash.defaultsdeep to 4.6.1 or the nearest later release, to fix CVE-2019-10744. 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.lodash-rails (RubyGems) fixed in 4.17.12
bundlerbundle update --conservative lodash-railsCheck what is installedbundle info lodash-railsPaste into Cursor, Lovable or Claude CodeUpgrade the RubyGems dependency lodash-rails to 4.17.12 or the nearest later release, to fix CVE-2019-10744. 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".