joi: Prototype pollution via a `__proto__` language key in custom messages
hapijs joi
hapijs joi
joi is a schema description language and data validator for JavaScript. From 16.0.0 until 17.13.6 and 18.2.5, the @hapi/joi package through 17.1.1 and the successor joi package contain prototype pollution in lib/messages.js, where exports.compile() and exports.merge() reuse inherited objects for attacker-controlled language keys supplied through messages(), message(), prefs({ messages }), Joi.extend({ messages }), or rule({ message }). A language key named __proto__ writes properties onto Object.prototype, and constructor writes to the Object function's static properties. A consuming application that gates on the presence of an inherited property can take the wrong branch for every inspected object. The flaw is not reachable from data that joi validates and requires an application to feed untrusted input directly into schema-construction configuration. This issue is fixed in joi versions 17.13.6 and 18.2.5; no fixed @hapi/joi version is available.
From the CVE record · GitHub_M
joi and @hapi/joi can pollute JavaScript prototypes when an application passes attacker-controlled language keys into message-related schema configuration. This can cause application checks for inherited properties to take the wrong branch. The flaw is not reachable through data that joi validates; the input does not specify an authentication or user-interaction requirement.
Check applications using npm joi >=17.2.0 <17.13.6 or >=18.0.0 <18.2.5, or npm @hapi/joi >=16.0.0 <=17.1.1.