CVE-2020-12330
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 · uneditedImproper permissions in the installer for the Intel(R) Falcon 8+ UAS AscTec Thermal Viewer, all versions, may allow an authenticated user to potentially enable escalation of privilege via local access.
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 confidenceThe installer for Intel Falcon 8+ UAS AscTec Thermal Viewer sets improper file system permissions, allowing an authenticated local user to modify executables, DLLs, or configuration files that subsequently run with elevated privileges, enabling local privilege escalation.
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 dataall versionsCVSS 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.
-
Verify if AscTec Thermal Viewer is installedCheck for the installation directory at typical locations: C:\Program Files\Intel\Falcon 8+ UAS AscTec Thermal Viewer\ or C:\Program Files (x86)\Intel\Falcon 8+ UAS AscTec Thermal Viewer\. Also check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Intel Falcon 8+ UAS AscTec Thermal Viewer'.Affected if The software is present on the system.
-
Identify the installation directoryIf found in the registry, read the InstallLocation value to determine the installation path. If the registry entry is missing, search the file system for folders containing 'AscTec' or 'ThermalViewer'.Affected if A directory containing AscTec Thermal Viewer files exists on the system.
-
Check write permissions on executable filesOpen Command Prompt as a standard (non-admin) user and attempt to write to .exe files in the installation directory, or use ICACLS from an admin command prompt to list permissions: icacls 'C:\Program Files\Intel\Falcon 8+ UAS AscTec Thermal Viewer\*.exe'Affected if Standard users or the 'Users' group have write (F) or write (W) permissions on executable files in the installation directory.
-
Check write permissions on DLL filesUse ICACLS to examine permissions on .dll files: icacls 'C:\Program Files\Intel\Falcon 8+ UAS AscTec Thermal Viewer\*.dll'Affected if Standard users or the 'Users' group have write permissions on DLL files that may be loaded by elevated processes.
-
Check write permissions on configuration filesUse ICACLS on config files: icacls 'C:\Program Files\Intel\Falcon 8+ UAS AscTec Thermal Viewer\*.ini' and icacls 'C:\Program Files\Intel\Falcon 8+ UAS AscTec Thermal Viewer\*.xml' and icacls 'C:\Program Files\Intel\Falcon 8+ UAS AscTec Thermal Viewer\*.cfg'Affected if Standard users or the 'Users' group have write permissions on configuration files that are read by elevated processes.
-
Verify if affected executables run with elevated privilegesExamine the application manifest or test by launching the .exe files while monitoring the resulting process privileges using Task Manager or Process Explorer, looking for 'Run as administrator' indicators or higher integrity levels.Affected if The executables run with administrator-level privileges while residing in a directory writable by standard users.
A user is affected if the Intel Falcon 8+ UAS AscTec Thermal Viewer is installed and standard users have write access to executables, DLLs, or configuration files that run with elevated privileges.
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 updated installer that sets restrictive permissions (minimum required for Users/Administrators). If no update available, manually audit and harden permissions on installed files using ICACLS to remove unnecessary write access for standard users.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12330 — 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-2020-12330 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