CVE-2017-2826

Name: CVE-2017-2826
Creator: NVD / NIST
Published: 2018-04-09T20:29:00.217+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 3.39%

Last modified Jun 17, 2026

CVE-2017-2826 is a vulnerability of currently unknown severity. 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. EPSS estimates a 3.39% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability

3.39%

87.3th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-200

Affected Software

Vendor	Product	Versions
Zabbix	Zabbix	2.4.0
Zabbix	Zabbix	2.4.1
Zabbix	Zabbix	2.4.2
Zabbix	Zabbix	2.4.3
Zabbix	Zabbix	2.4.4
Zabbix	Zabbix	2.4.5
Zabbix	Zabbix	2.4.6
Zabbix	Zabbix	2.4.7
Zabbix	Zabbix	2.4.8
Zabbix	Zabbix	2.4.9
Debian	Debian Linux	8.0

References

https://lists.debian.org/debian-lts-announce/2019/03/msg00010.htmlMailing List, Third Party Advisory
https://talosintelligence.com/vulnerability_reports/TALOS-2017-0327Exploit, Third Party Advisory
https://lists.debian.org/debian-lts-announce/2019/03/msg00010.htmlMailing List, Third Party Advisory
https://talosintelligence.com/vulnerability_reports/TALOS-2017-0327Exploit, Third Party Advisory

Timeline

Published: Apr 9, 2018
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-2826?

How severe is CVE-2017-2826?

Severity scoring for CVE-2017-2826 is pending analysis. The EPSS model estimates a 3.39% probability of exploitation in the next 30 days.

How do I fix CVE-2017-2826?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-2826?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST