An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)
The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.
Link | Tags |
---|---|
https://hackerone.com/bugs?subject=user&report_id=894259 | permissions required |
https://github.com/ajv-validator/ajv/tags | third party advisory |
https://github.com/ajv-validator/ajv/releases/tag/v6.12.3 | third party advisory release notes |
https://security.netapp.com/advisory/ntap-20240621-0007/ |