Debian LinuxOperating system · Debian
CVE-2019-15132
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 · uneditedZabbix through 4.4.0alpha1 allows User Enumeration. With login requests, it is possible to enumerate application usernames based on the variability of server responses (e.g., the "Login name or password is incorrect" and "No permissions for system access" messages, or just blocking for a number of seconds). This affects both api_jsonrpc.php and index.php.
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 confidenceZabbix through 4.4.0alpha1 contains a user enumeration vulnerability in the login functionality (api_jsonrpc.php and index.php). The server returns different responses for valid vs. invalid usernames - either distinct error messages like 'Login name or password is incorrect' versus 'No permissions for system access', or differential account blocking timing. This allows attackers to harvest valid usernames for subsequent attacks.
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
Debian LinuxOperating system
= 9.0<= 4.0.26>= 5.0.0, <= 5.0.5>= 5.2.0, <= 5.2.1= 4.4.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 versionCheck the Zabbix version by reviewing the frontend or checking the package version (e.g., dpkg -l zabbix-frontend-php or rpm -qi zabbix-web on the server)Affected if The installed version matches one of the affected ranges: <= 4.0.26, >= 5.0.0 to <= 5.0.5, >= 5.2.0 to <= 5.2.1, or exactly 4.4.0
-
Identify the login endpoint URLsLocate the Zabbix web interface login pages at api_jsonrpc.php and index.php within the web server document root (commonly /usr/share/zabbix or /var/www/html/zabbix)Affected if These files exist and are accessible from the web, indicating Zabbix frontend is deployed
-
Test error message for non-existent usernameSubmit a login request to api_jsonrpc.php or index.php with a clearly invalid username (e.g., nonexistentuser123) and any password, then capture the returned error messageAffected if The error message differs from what would be shown for a valid username, or returns a generic 'user not found' type response
-
Test error message for valid username with wrong passwordSubmit a login request using a known-valid username with an incorrect password, then capture the returned error messageAffected if The error message differs from the invalid username case (e.g., shows 'No permissions for system access' vs 'Login name or password is incorrect'), confirming the enumeration vector
-
Verify uniform error messaging configurationReview the Zabbix authentication settings in the frontend (Configuration -> Authentication) or inspect the authentication failure message strings in the Zabbix source files (include/classes/api/CUser.php or similar)Affected if Error messages are not unified - different messages are returned based on whether the username exists in the system
You are affected if your Zabbix installation version falls within the affected ranges AND your login page returns distinguishable error messages for valid versus invalid usernames, allowing an attacker to enumerate valid accounts.
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 dataConfigure uniform authentication error messages for all login failures regardless of username validity, and implement rate limiting or progressive delays to prevent automated enumeration. Upgrade to Zabbix 4.4.0beta1 or later where this issue was reportedly fixed.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15132 — 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-2019-15132 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