This weekExploitable · Confirmed
deobfuscator: Synchrony deobfuscator prototype pollution vulnerability leading to arbitrary code execution
There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.
Does it affect what I run?
deobfuscator (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- deobfuscator (npm): from 2.0.1, before 2.4.4
The fix
deobfuscator (npm) fixed in 2.4.4
npmnpm install deobfuscator@2.4.4pnpmpnpm add deobfuscator@2.4.4yarnyarn add deobfuscator@2.4.4bunbun add deobfuscator@2.4.4Check what is installednpm ls deobfuscatorPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency deobfuscator to 2.4.4 or the nearest later release, to fix CVE-2023-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))