CVE-2012-6086 json
libs/zbxmedia/eztexting.c in Zabbix 1.8.x before 1.8.18rc1, 2.0.x before 2.0.8rc1, and 2.1.x before 2.1.2 does not properly set the CURLOPT…
published 2014-01-29 12 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5957
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
libs/zbxmedia/eztexting.c in Zabbix 1.8.x before 1.8.18rc1, 2.0.x before 2.0.8rc1, and 2.1.x before 2.1.2 does not properly set the CURLOPT_SSL_VERIFYHOST option for libcurl, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.
Patch / fix
- zabbix Debian 14, Debian 13, Debian 12 1:2.0.7+dfsg-1
debian advisories DEBIAN-CVE-2012-6086
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2012-6086 updated cvss 4.3
zabbix: Improper use of cURL API might lead to improper SSL certificate verification (MiTM)
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.90% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
-
support.zabbix.com
/browse/ZBX-5924
vendor-advisory
-
securityfocus.com
/bid/57103
vdb-entry, third-party-advisory
-
openwall.com
/lists/oss-security/2013/01/03/1
mailing-list, issue-tracking
Sources
- CVE List CVE-2012-6086
- NVD CVE-2012-6086
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.