FedoraOperating system · Fedoraproject
CVE-2014-1685
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 Frontend in Zabbix before 1.8.20rc2, 2.0.x before 2.0.11rc2, and 2.2.x before 2.2.2rc1 allows remote "Zabbix Admin" users to modify the media of arbitrary users via unspecified vectors.
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 · high confidenceThe Zabbix frontend before versions 1.8.20rc2, 2.0.11rc2, and 2.2.2rc1 contains an authorization flaw where a user with 'Zabbix Admin' privileges can modify the notification media (email, SMS, etc.) of any other user in the system. This represents a privilege escalation issue within the application's user management functionality.
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
FedoraOperating system
= 19= 20<= 1.8.19= 1.8= 1.8.1= 1.8.2= 1.8.3= 1.8.15= 1.8.16= 1.8.18= 2.0.0= 2.0.1= 2.0.2= 2.0.3CVSS 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
- Single
- Confidentiality
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:N/I:P/A:P
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.
-
Identify Zabbix versionAccess the Zabbix frontend login page or the Dashboard, then navigate to the footer or 'About' section which typically displays the Zabbix version. Alternatively, check the Zabbix server or frontend configuration files for version information.Affected if The installed version is <= 1.8.19, or is one of 1.8.x versions 1.8, 1.8.1, 1.8.2, 1.8.3, 1.8.15, 1.8.16, 1.8.18, or 2.0.x versions 2.0.0, 2.0.1, 2.0.2, 2.0.3, or if running on Fedora 19 or 20 with affected Zabbix packages.
-
Confirm Zabbix frontend is in useVerify that the Zabbix web interface is deployed and accessible. This vulnerability affects only the frontend component, not the Zabbix server or agent alone.Affected if The Zabbix web frontend is running and accessible on the network.
-
Check for Zabbix Admin usersLog into the Zabbix frontend as an administrator and navigate to the Users or User Group configuration section. Review which users are assigned the 'Zabbix Admin' role or equivalent privileges.Affected if There are one or more users with 'Zabbix Admin' privileges configured in the system.
-
Verify notification media access controlsAs a user with 'Zabbix Admin' privileges, attempt to access the media settings of a different user (navigate to Users > Media for a user other than your own) to confirm whether modification is possible without proper authorization checks.Affected if A 'Zabbix Admin' user can modify notification media (email, SMS, etc.) for other users in the system, indicating the authorization flaw is present.
The environment is affected if running a Zabbix frontend version <= 1.8.19, 2.0.0-2.0.3, or certain 1.8.x point releases, AND the web frontend is accessible, AND there are users with 'Zabbix Admin' privileges who can access other users' notification media settings.
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.20rc2 or later for the 1.8.x branch, 2.0.11rc2 or later for 2.0.x, or 2.2.2rc1 or later for 2.2.x. If upgrading is not immediately possible, review user role permissions and restrict Zabbix Admin access to only trusted personnel.
Fix this in Fedora
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1685 — 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-2014-1685 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