CVE-2017-2826: Infoleak
First published: Mon Apr 09 2018(Updated: )
An information disclosure vulnerability exists in the iConfig proxy request of Zabbix server 2.4.X. A specially crafted iConfig proxy request can cause the Zabbix server to send the configuration information of any Zabbix proxy, resulting in information disclosure. An attacker can make requests from an active Zabbix proxy to trigger this vulnerability.
Credit: talos-cna@cisco.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Zabbix Zabbix | =2.4.0 | |
| Zabbix Zabbix | =2.4.0-rc1 | |
| Zabbix Zabbix | =2.4.0-rc2 | |
| Zabbix Zabbix | =2.4.0-rc3 | |
| Zabbix Zabbix | =2.4.1 | |
| Zabbix Zabbix | =2.4.1-rc1 | |
| Zabbix Zabbix | =2.4.1-rc2 | |
| Zabbix Zabbix | =2.4.2 | |
| Zabbix Zabbix | =2.4.2-rc1 | |
| Zabbix Zabbix | =2.4.3 | |
| Zabbix Zabbix | =2.4.3-rc1 | |
| Zabbix Zabbix | =2.4.4 | |
| Zabbix Zabbix | =2.4.4-rc1 | |
| Zabbix Zabbix | =2.4.5 | |
| Zabbix Zabbix | =2.4.5-rc1 | |
| Zabbix Zabbix | =2.4.6 | |
| Zabbix Zabbix | =2.4.6-rc1 | |
| Zabbix Zabbix | =2.4.7 | |
| Zabbix Zabbix | =2.4.7-rc1 | |
| Zabbix Zabbix | =2.4.8 | |
| Zabbix Zabbix | =2.4.8-rc1 | |
| Zabbix Zabbix | =2.4.9 | |
| Zabbix Zabbix | =2.4.9-rc1 | |
| Debian Debian Linux | =8.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2017-2826?
CVE-2017-2826 is an information disclosure vulnerability in the iConfig proxy request of Zabbix server 2.4.X.
What is the severity of CVE-2017-2826?
The severity of CVE-2017-2826 is medium.
How can an attacker exploit CVE-2017-2826?
An attacker can exploit CVE-2017-2826 by sending a specially crafted iConfig proxy request to the Zabbix server, causing it to disclose the configuration information of any Zabbix proxy.
Which versions of Zabbix server are affected by CVE-2017-2826?
Zabbix server versions 2.4.0 to 2.4.9, including release candidates, are affected by CVE-2017-2826.
How can I fix CVE-2017-2826?
To fix CVE-2017-2826, upgrade to a version of Zabbix server that is not affected by the vulnerability.
- collector/nvd-index
- agent/author
- agent/severity
- agent/weakness
- agent/references
- agent/tags
- agent/type
- agent/softwarecombine
- agent/last-modified-date
- vendor/zabbix
- canonical/zabbix zabbix
- version/zabbix zabbix/2.4.0
- version/zabbix zabbix/2.4.0-rc1
- version/zabbix zabbix/2.4.0-rc2
- version/zabbix zabbix/2.4.0-rc3
- version/zabbix zabbix/2.4.1
- version/zabbix zabbix/2.4.1-rc1
- version/zabbix zabbix/2.4.1-rc2
- version/zabbix zabbix/2.4.2
- version/zabbix zabbix/2.4.2-rc1
- version/zabbix zabbix/2.4.3
- version/zabbix zabbix/2.4.3-rc1
- version/zabbix zabbix/2.4.4
- version/zabbix zabbix/2.4.4-rc1
- version/zabbix zabbix/2.4.5
- version/zabbix zabbix/2.4.5-rc1
- version/zabbix zabbix/2.4.6
- version/zabbix zabbix/2.4.6-rc1
- version/zabbix zabbix/2.4.7
- version/zabbix zabbix/2.4.7-rc1
- version/zabbix zabbix/2.4.8
- version/zabbix zabbix/2.4.8-rc1
- version/zabbix zabbix/2.4.9
- version/zabbix zabbix/2.4.9-rc1
- vendor/debian
- canonical/debian debian linux
- version/debian debian linux/8.0