CVE-2013-1364
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe user.login function in Zabbix versions before 1.8.16 and 2.x before 2.0.5rc1 contains a vulnerability allowing remote attackers to override LDAP configuration settings through the 'cnf' parameter. This parameter injection could allow manipulation of authentication settings or potential bypass of LDAP-based access controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.8.15= 2.0.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Zabbix versionQuery the Zabbix API version endpoint, check the frontend footer, or run 'zabbix_server -V' on the server. For API: send GET request to /apiinfo/version or check response header.Affected if version is 1.8.15 or lower, OR version is 2.0.0 through 2.0.4
-
Confirm LDAP authentication is configuredLog into Zabbix frontend as administrator, navigate to Administration > Authentication > LDAP settings. Or query the 'config' table in the Zabbix database for ldap_configured value.Affected if LDAP authentication is enabled (ldap_configured = 1 or LDAP settings are populated)
-
Verify user.login API method is accessibleSend a POST request to http(s)://<zabbix-server>/apirpc.php with JSON body: {"jsonrpc":"2.0","method":"user.login","params":{"user":"admin","password":"invalid"},"id":1}. Check if the API accepts the 'cnf' parameter.Affected if user.login API responds and accepts a 'cnf' parameter without proper authorization
-
Check external exposure of Zabbix interfaceReview network configuration or firewall rules to determine if the Zabbix web interface/API is accessible from untrusted networks (internet-facing).Affected if Zabbix frontend or API is directly exposed to the internet without VPN or IP restriction
You are affected if your Zabbix version falls within 1.8.x <= 1.8.15 or 2.0.0-2.0.4 AND LDAP authentication is enabled AND the user.login API endpoint is accessible to attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Zabbix to version 1.8.16, 2.0.5rc1, or later to obtain the patched code that properly validates and authorizes the cnf parameter. If immediate upgrade is not feasible, review and restrict access to the user.login API endpoint.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1364 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-1364 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data