CVE-2020-15366
Published: 15 July 2020
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.)
Priority
Status
| Package | Release | Status |
|---|---|---|
|
node-ajv Launchpad, Ubuntu, Debian |
bionic |
Needs triage
|
| eoan |
Ignored
(end of life)
|
|
| focal |
Needs triage
|
|
| groovy |
Not vulnerable
(6.12.4-1)
|
|
| hirsute |
Not vulnerable
(6.12.4-1)
|
|
| impish |
Not vulnerable
(6.12.4-1)
|
|
| jammy |
Not vulnerable
(6.12.4-1)
|
|
| kinetic |
Not vulnerable
(6.12.4-1)
|
|
| lunar |
Not vulnerable
(6.12.4-1)
|
|
| mantic |
Not vulnerable
(6.12.4-1)
|
|
| trusty |
Does not exist
|
|
| upstream |
Needs triage
|
|
| xenial |
Does not exist
|
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 5.6 |
| Attack vector | Network |
| Attack complexity | High |
| Privileges required | None |
| User interaction | None |
| Scope | Unchanged |
| Confidentiality | Low |
| Integrity impact | Low |
| Availability impact | Low |
| Vector | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L |