CVE-2022-0564
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 · uneditedA vulnerability in Qlik Sense Enterprise on Windows could allow an remote attacker to enumerate domain user accounts. An attacker could exploit this vulnerability by sending authentication requests to an affected system. A successful exploit could allow the attacker to compare the response time that are returned by the affected system to determine which accounts are valid user accounts. Affected systems are only vulnerable if they have LDAP configured. The affected URI is /internal_forms_authentication/ the response time of the form is longer if the supplied user does not exists and shorter if the user exists.
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 confidenceQlik Sense Enterprise on Windows contains a timing-based username enumeration vulnerability in the /internal_forms_authentication/ endpoint. Attackers can determine valid domain user accounts by measuring response times—the system responds slower for non-existent LDAP users compared to existing ones, enabling account enumeration through repeated authentication requests.
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>= 14.0, < 14.44.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.
-
Identify the installed Qlik Sense versionAccess the Qlik Management Console or check the productAbout page to determine the exact version number of Qlik Sense Enterprise on WindowsAffected if The installed version falls within >= 14.0 and < 14.44.0
-
Confirm LDAP user authentication is configuredVerify that the Qlik Sense deployment uses LDAP or Active Directory integration for user authentication through the Identity Provider settingsAffected if LDAP/AD authentication is enabled and the system validates users against an LDAP directory
-
Verify exposure of the authentication endpointCheck network accessibility of the /internal_forms_authentication/ path on the Qlik Sense server - determine if it is reachable from untrusted networksAffected if The endpoint is externally accessible without network restrictions
-
Review authentication logging for enumeration patternsExamine Qlik Sense audit logs and authentication logs for repeated login attempts targeting different usernames, looking for timing anomaliesAffected if Logs show consistent timing differences between valid and invalid username attempts
-
Check for existing rate limiting or account lockout policiesReview the authentication security configuration to determine if rate limiting or account lockout thresholds are configured on the Qlik Sense proxy or load balancerAffected if No rate limiting or account lockout mechanisms are configured for the authentication endpoint
The environment is affected if Qlik Sense version is between 14.0 and 14.44.0, LDAP authentication is enabled, and the vulnerable endpoint is accessible without protective timing or rate-limiting controls.
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 · scoped14.44.0
Implement rate limiting and account lockout policies on the authentication endpoint; apply vendor patch when available; consider network-level filtering to limit attack surface.
14.44.0
- Verify the current Qlik Sense version by accessing the Qlik Management Console (QMC) or checking the version via the Qlik Sense Repository Service (QRS) API
- Ensure you have a complete backup of the Qlik Sense repository database and configuration
- Take a snapshot of the virtual machine or perform a system state backup
- Schedule a maintenance window as the upgrade will require service restarts
- Download Qlik Sense version 14.44.0 or later from the Qlik download portal (requires valid Qlik account)
- Run the Qlik Sense installer on the central node first, following the on-screen prompts
- After the central node upgrade, the dependent services will automatically upgrade on remaining nodes
- Verify all services are running correctly post-upgrade via the QMC
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-2022-0564 — 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-2022-0564 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