Low severity · published Apr 9, 2018
CVE-2017-2826
An information disclosure vulnerability exists in the iConfig proxy request of Zabbix server 2.4.X
3.7
CVSS
3.3%
EPSS
No
On KEV
Description
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.
CVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Confidentiality
Low
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)3.3% · higher than 88% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
ZA
Zabbix · Zabbix
2.4.0; 2.4.0; 2.4.0; 2.4.0; 2.4.1; 2.4.1; +17 more · source: NVD
DL
Debian Linux · Debian
8.0 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2017-2826
CVE.org
https://www.cve.org/CVERecord?id=CVE-2017-2826
Mailing List
https://lists.debian.org/debian-lts-announce/2019/03/msg00010.html
Exploit
https://talosintelligence.com/vulnerability_reports/TALOS-2017-0327
More from Zabbix
9.8
CVE-2022-23131
Unsafe client-side session storage leading to authentication bypass/instance takeover via Zabbix Frontend with configured SAML
5.3
CVE-2022-23134
Possible view of the setup pages by unauthenticated users if config file already exists
9.9
CVE-2024-42327
A non-admin user account on the Zabbix frontend with the default User role, or with any other role that gives API access can exploit this vulnerability
9.8
CVE-2022-43516
A Firewall Rule which allows all incoming TCP connections to all programs from any source and to all ports is created in Windows Firewall after Zabbix agent installation (MSI)
9.8
CVE-2020-11800
Zabbix Server 2.2.x and 3.0.x before 3.0.31, and 3.2 allows remote attackers to execute arbitrary code