dbcve.org
Qlikview ServerApplication · Qlik

CVE-2019-11628

MEDIUM · 6.5 CVSS v3.0 Published 2019-05-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
An issue was discovered in QlikView Server before 11.20 SR19, 12.00 and 12.10 before 12.10 SR11, 12.20 before SR9, and 12.30 before SR2; and Qlik Sense Enterprise and Qlik Analytics Platform installations that lack these patch levels: February 2018 Patch 4, April 2018 Patch 3, June 2018 Patch 3, September 2018 Patch 4, November 2018 Patch 4, or February 2019 Patch 2. An authenticated user may be able to bypass intended file-read restrictions via crafted Browser requests.

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 confidence

This vulnerability allows authenticated users to bypass intended file-read restrictions in QlikView Server and Qlik Sense Enterprise through crafted HTTP Browser requests. The issue is a path traversal or authorization bypass that permits unauthorized file system access by manipulating request parameters.

MitigationApply the vendor-provided patches: QlikView Server to SR19, 12.10 SR11, 12.20 SR9, or 12.30 SR2; Qlik Sense installations to February 2018 Patch 4, April 2018 Patch 3, June 2018 Patch 3, September 2018 Patch 4, November 2018 Patch 4, or February 2019 Patch 2.

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
Qlikview ServerApplication
Affected:= 11.20= 12.00= 12.10= 12.20= 12.30
Qlik AnalyticsApplication
Affected:= april_2018= february_2018= february_2019= june_2017= june_2018= november_2017= november_2018= september_2017= september_2018
Qlik SenseApplication
Affected:= april_2018= february_2018= february_2019= june_2017= june_2018= november_2017= november_2018= september_2017= september_2018

CVSS 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
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Qlik product version
    Access the Qlik Management Console (QMC) or the about page of the Qlik web interface (typically at /qmc/about or /hub/about) to view the exact version and build number of the installed Qlik software
    Affected if The displayed version matches any of the following: QlikView Server 11.20, 12.00, 12.10, 12.20, or 12.30; Qlik Analytics or Qlik Sense versions april_2018, february_2018, february_2019, june_2017, june_2018, november_2017, november_2018, september_2017, or september_2018
  2. Confirm web access is enabled
    Verify that the Qlik web service (Qlik Sense Proxy Service or QlikView Web Server) is running and accessible by attempting to reach the login page via HTTP/HTTPS on the standard Qlik ports (typically 80/443 or 4242/4747)
    Affected if The web interface is accessible without network restrictions, meaning an authenticated user could potentially send crafted HTTP requests to the server
  3. Verify authentication is configured
    Check that Qlik authentication is properly configured and that the server allows user logins through the QMC or directory service configurations
    Affected if User authentication is enabled and functional, which is required for this vulnerability to be exploitable (the flaw affects authenticated users)
  4. Check for existing patches
    Review the currently installed version against the patched versions: QlikView Server should be at SR19 (11.20), SR11 (12.10), SR9 (12.20), or SR2 (12.30); Qlik Sense should have Patch 4 or higher for February/April/June/September/November 2018, or Patch 2 for February 2019
    Affected if The installed version is below these patch levels, indicating the security fix has not been applied

You are affected if your QlikView Server or Qlik Sense installation version matches any of the listed affected versions and the web interface with authentication is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided patches: QlikView Server to SR19, 12.10 SR11, 12.20 SR9, or 12.30 SR2; Qlik Sense installations to February 2018 Patch 4, April 2018 Patch 3, June 2018 Patch 3, September 2018 Patch 4, November 2018 Patch 4, or February 2019 Patch 2.

Fix this in Qlikview Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-11628 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-11628 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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