https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 10 Oct 2026 08:23:29 +0000 https://cve.radiocsirt.org/vuln/cve-2021-21368 <p><strong>Affected:</strong> mcollina msgpack5</p> <p>msgpack5 is a msgpack v5 implementation for node.js and the browser. In msgpack5 before versions 3.6.1, 4.5.1, and 5.2.1 there is a &#34;Prototype Poisoning&#34; vulnerability. When msgpack5 decodes a map containing a key &#34;__proto__&#34;, it assigns the decoded value to __proto__. Object.prototype.__proto__ is an accessor property for the receiver&#39;s prototype. If the value corresponding to the key __proto__ decodes to an object or null, msgpack5 sets the decoded object&#39;s prototype to that value. An attacker who can submit crafted MessagePack data to a service can use this to produce values that appear to be of other types; may have unexpected prototype properties and methods (for example length, numeric properties, and push et al if __proto__&#39;s value decodes to an Array); and/or may throw unexpected exceptions when used (for example if the __proto__ value decodes to a Map or Date). Other unexpected behavior might be produced for other types. There is no effect on the global prototype. This &#34;prototype poisoning&#34; is sort of a very limited inversion of a prototype pollution attack. Only the decoded value&#39;s prototype is affected, and it can only be set to msgpack5 values (though if the victim makes use of custom codecs, anything could be a msgpack5 value). We have not found a way to escalate this to true prototype pollution (absent other bugs in the consumer&#39;s code). This has been fixed in msgpack5 version 3.6.1, 4.5.1, and 5.2.1. See the referenced GitHub Security Advisory for an example a…</p> <p><strong>Affected:</strong> mcollina msgpack5</p> <p>msgpack5 is a msgpack v5 implementation for node.js and the browser. In msgpack5 before versions 3.6.1, 4.5.1, and 5.2.1 there is a &#34;Prototype Poisoning&#34; vulnerability. When msgpack5 decodes a map containing a key &#34;__proto__&#34;, it assigns the decoded value to __proto__. Object.prototype.__proto__ is an accessor property for the receiver&#39;s prototype. If the value corresponding to the key __proto__ decodes to an object or null, msgpack5 sets the decoded object&#39;s prototype to that value. An attacker who can submit crafted MessagePack data to a service can use this to produce values that appear to be of other types; may have unexpected prototype properties and methods (for example length, numeric properties, and push et al if __proto__&#39;s value decodes to an Array); and/or may throw unexpected exceptions when used (for example if the __proto__ value decodes to a Map or Date). Other unexpected behavior might be produced for other types. There is no effect on the global prototype. This &#34;prototype poisoning&#34; is sort of a very limited inversion of a prototype pollution attack. Only the decoded value&#39;s prototype is affected, and it can only be set to msgpack5 values (though if the victim makes use of custom codecs, anything could be a msgpack5 value). We have not found a way to escalate this to true prototype pollution (absent other bugs in the consumer&#39;s code). This has been fixed in msgpack5 version 3.6.1, 4.5.1, and 5.2.1. See the referenced GitHub Security Advisory for an example a…</p> https://cve.radiocsirt.org/vuln/cve-2021-21368