Within Zabbix, users have the ability to directly modify memory pointers in the JavaScript engine.
The product obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Zabbix | Zabbix | 6.0.0 (including) | 6.0.30 (including) |
| Zabbix | Zabbix | 6.4.0 (including) | 6.4.15 (including) |
| Zabbix | Zabbix | 7.0.0 (including) | 7.0.0 (including) |
| Zabbix | Ubuntu | trusty/esm | * |
An attacker can supply a pointer for memory locations that the product is not expecting. If the pointer is dereferenced for a write operation, the attack might allow modification of critical state variables, cause a crash, or execute code. If the dereferencing operation is for a read, then the attack might allow reading of sensitive data, cause a crash, or set a variable to an unexpected value (since the value will be read from an unexpected memory location). There are several variants of this weakness, including but not necessarily limited to: