CVE-2021-41989
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 · uneditedQlik QlikView through 12.60.20100.0 creates a Temporary File in a Directory with Insecure Permissions.
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 QlikView through version 12.60.20100.0 creates temporary files in directories with insecure permissions, allowing a local attacker to potentially manipulate these files and escalate privileges to execute code with elevated rights.
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<= 12.60.20100.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 QlikView installation location and versionCheck the QlikView installation directory (typically C:\Program Files\QlikView or C:\Program Files (x86)\QlikView) and locate the version information, often found in the executable properties or in a version file within the installation folderAffected if The installed version is 12.60.20100.0 or lower
-
Locate QlikView temporary file directoriesIdentify directories where QlikView stores temporary files - commonly found in the QlikView installation directory under folders named 'Temp', 'temp', or in user profile directories (AppData\Local\QlikView or AppData\Roaming\QlikView)Affected if Temporary directories exist within or associated with the QlikView installation
-
Check permissions on identified temporary directoriesRight-click each temporary directory, go to Properties > Security, and verify the effective permissions. Use 'icacls' command (e.g., icacls "C:\Program Files\QlikView\Temp") to view ACLs in detailAffected if Directories grant write or modify access to users other than the owner or Administrators group, or have permissions more permissive than 750 for directories and 640 for files
-
Scan for newly created temporary files in QlikView directoriesUse File Explorer or PowerShell (Get-ChildItem -Path "C:\Program Files\QlikView" -Recurse -Filter "*.tmp") to enumerate .tmp files and check their parent directory permissionsAffected if Temporary files exist in directories with overly permissive access controls allowing unauthorized modification
-
Verify QlikView service account permissionsOpen Services (services.msc), locate the QlikView service, check the 'Log On As' account, then verify that this account's home directory and temp directories used by this service have restrictive permissionsAffected if The service runs under an account whose associated temp directories are writable by low-privilege users
A system is affected if QlikView version 12.60.20100.0 or lower is installed AND temporary directories used by QlikView have permissions more permissive than the recommended 750 for directories and 640 for files, allowing unauthorized local users to manipulate temp files.
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 dataApply vendor-supplied patch when released; ensure temporary directories used by QlikView have restrictive permissions (minimum 750 for directories, 640 for files) and monitor for unauthorized file creation.
- Consultation2.0 h
- Implementation1.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41989 — 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-2021-41989 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