Forge: Prototype Pollution in forge.http cookie handling via a malicious Set-Cookie

[ Description ]Official description

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the forge.http client stored cookie names and paths from Set-Cookie response headers in ordinary JavaScript objects. A malicious server could use the cookie name __proto__ so that the attacker-controlled cookie path was written as a property on Object.prototype, or use inherited names such as constructor to modify Object. An empty cookie value could use the removal path to delete an inherited Object.prototype property. Applications using forge.http directly or through forge.xhr are affected; applications that do not use forge.http are unaffected. This issue is fixed in version 1.4.1.

[ Fixes ]Fixes and patches

• node-forge 1.4.1Fixed version · GitHub Advisories · npm package node-forge: upgrade to 1.4.1 or later (affected <= 1.4.0)
• Patch on github.comVendor patch or bulletin · NVD · Reference tagged 'Patch' by NVD

[ Packages ]Affected open-source packages

• node-forge npmAffected <= 1.4.0 · fixed in 1.4.1 · GHSA-6wvx-3r32-xmcg

[ References ]References

• github.com/digitalbazaar/forge/commit/797c3f816a22748a96fceebb34eb3a6716853991Patch
• github.com/digitalbazaar/forge/releases/tag/v1.4.1Release Notes
• github.com/digitalbazaar/forge/security/advisories/GHSA-6wvx-3r32-xmcgExploitMitigationVendor Advisory