EIQ-2020-0011
    
| ID | EIQ-2020-0011 | 
| CVE | |
| Description | ajv enables prototype pollution | 
| Date | 20 Jul 2020 | 
| Severity | 3 - HIGH | 
| CVSSv3 score | 8.1 (Snyk score) | 
| Status | 
 | 
| Assessment | Despite the high CVSS score, this vulnerability has very limited impact on the platform: 
 ajv versions 6.12.2 and earlier could enable an attacker to inject properties into JavaScript prototype objects by exploiting a vulnerability affecting JSON schema validation: a carefully crafted JSON schema could allow execution of other code by prototype pollution. An attacker could add or modify object prototype properties of Object.prototype with a constructor or a __proto__ payload. In this scenario, remote code execution and property injection attempts would be blocked, and it would not be possible to use these techniques. A signed-in platform user without admin access rights, and with at least the modify blob-uploads (to manually upload PDF files to the platform) and the read files (to view PDF files in the platform GUI) permissions, could exploit the vulnerability by: 
 The client-side DoS would negatively impact web browser performance, and the browser would hang or freeze. | 
| Mitigation | At the moment, it is not possible to globally upgrade ajv, because it occurs at least once as a sub-dependency. We cannot control these dependencies. We are addressing this issue in a future planned release by enforcing the platform and relevant frontend dependencies to use ajv version 6.12.3 or later. 
 | 
| Affected versions | 2.8.0 and earlier. | 
| Notes | For more information, see: 
 See also: | 
< Back to all security issues and mitigation actions
In release notes 2.8.0
In release notes 2.9.0