For your digest
passport-saml, node-saml: Signature bypass via multiple root elements
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
- passport-saml (npm): every version, before 3.2.2
- node-saml (npm): every version, before 4.0.0-beta.5
- @node-saml/node-saml (npm): every version, before 4.0.0-beta.5
- @node-saml/passport-saml (npm): every version, before 4.0.0-beta.3
The fix
passport-saml (npm) fixed in 3.2.2
npmnpm install passport-saml@3.2.2pnpmpnpm add passport-saml@3.2.2yarnyarn add passport-saml@3.2.2bunbun add passport-saml@3.2.2Check what is installednpm ls passport-samlPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency passport-saml to 3.2.2 or the nearest later release, to fix CVE-2022-39299. 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.node-saml (npm) fixed in 4.0.0-beta.5
npmnpm install node-saml@4.0.0-beta.5pnpmpnpm add node-saml@4.0.0-beta.5yarnyarn add node-saml@4.0.0-beta.5bunbun add node-saml@4.0.0-beta.5Check what is installednpm ls node-samlPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency node-saml to 4.0.0-beta.5 or the nearest later release, to fix CVE-2022-39299. 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.@node-saml/node-saml (npm) fixed in 4.0.0-beta.5
npmnpm install "@node-saml/node-saml@4.0.0-beta.5"pnpmpnpm add "@node-saml/node-saml@4.0.0-beta.5"yarnyarn add "@node-saml/node-saml@4.0.0-beta.5"bunbun add "@node-saml/node-saml@4.0.0-beta.5"Check what is installednpm ls @node-saml/node-samlPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @node-saml/node-saml to 4.0.0-beta.5 or the nearest later release, to fix CVE-2022-39299. 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.@node-saml/passport-saml (npm) fixed in 4.0.0-beta.3
npmnpm install "@node-saml/passport-saml@4.0.0-beta.3"pnpmpnpm add "@node-saml/passport-saml@4.0.0-beta.3"yarnyarn add "@node-saml/passport-saml@4.0.0-beta.3"bunbun add "@node-saml/passport-saml@4.0.0-beta.3"Check what is installednpm ls @node-saml/passport-samlPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @node-saml/passport-saml to 4.0.0-beta.3 or the nearest later release, to fix CVE-2022-39299. 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".