CVE-2013-1364 json
The user.login function in Zabbix before 1.8.16 and 2.x before 2.0.5rc1 allows remote attackers to override LDAP configuration via the cnf…
published 12y ago modified 4mo ago also EUVD-2013-1403
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
The user.login function in Zabbix before 1.8.16 and 2.x before 2.0.5rc1 allows remote attackers to override LDAP configuration via the cnf parameter.
Patch / fix
- zabbix Debian 14, Debian 13, Debian 12 1:2.0.4+dfsg-2
debian advisories DEBIAN-CVE-2013-1364
Is CVE-2013-1364 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-1364 updated cvss 5.8
zabbix: possible to override LDAP configuration parameters via the API
-
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
2.17% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
security.gentoo.org
/glsa/glsa-201311-15.xml
vendor-advisory
-
zabbix.com
/rn1.8.16.php
vendor-advisory
-
zabbix.com
/rn2.0.5rc1.php
vendor-advisory
-
secunia.com
/advisories/55824
third-party-advisory, vendor-advisory
- support.zabbix.com /browse/ZBX-6097
-
securityfocus.com
/bid/57471
vdb-entry
Sources
- CVE List CVE-2013-1364
- NVD CVE-2013-1364
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.