CVE-2024-36460
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 front-end audit log allows viewing of unprotected plaintext passwords, where the passwords are displayed in plain text.
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 front-end audit log component displays user passwords in plaintext, allowing anyone with access to the audit log to view unprotected credentials in clear text. This represents a critical information disclosure where sensitive authentication credentials are exposed without encryption or masking.
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>= 5.0.0, <= 5.0.42>= 6.0.0, <= 6.0.30>= 6.4.0, <= 6.4.15= 7.0.0CVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Identify installed Zabbix versionCheck the Zabbix frontend footer or access the Zabbix API endpoint /api/version, or check the package version (rpm -qa zabbix* or dpkg -l | grep zabbix)Affected if The installed version falls within 5.0.0-5.0.42, 6.0.0-6.0.30, 6.4.0-6.4.15, or equals 7.0.0
-
Confirm audit log feature is enabledLog into Zabbix frontend as administrator, navigate to Reports > Audit log, or query the auditlog table in the Zabbix databaseAffected if Audit logging is enabled and accessible (default behavior)
-
Check for user password-related audit entriesReview audit log entries for actions involving user password changes or user creation; examine if password fields appear in plaintext within the audit detailsAffected if Audit log entries display password field contents in clear text rather than masked or hashed values
You are affected if your Zabbix installation version is within the affected ranges and users with audit log access can view plaintext password values in audit records.
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.
dbcve · scopedDisable plaintext password display in audit log interfaces by masking or removing password fields from log output; audit and remediate password storage to ensure proper hashing is in place.
Upgrade to Zabbix 5.0.43, 6.0.31, 6.4.16, or 7.0.1 or later (depending on your major version branch)
- 1. Back up your current Zabbix configuration and database before performing any upgrade
- 2. Download the appropriate fixed version of Zabbix from the official Zabbix download page (zabbix.com/download) or your distribution's package repository
- 3. For Zabbix Server: Stop the Zabbix server service
- 4. Upgrade Zabbix server, front-end, and agent packages to the fixed version
- 5. Start the Zabbix server service
- 6. Verify the audit log no longer displays plaintext passwords by checking recent audit entries
- 7. Clear any existing audit logs that may contain plaintext passwords if they are no longer needed for compliance
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36460 — 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-2024-36460 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