dbcve.org
Antivirus ProApplication · Quickheal

CVE-2018-8090

HIGH · 7.8 CVSS v3.1 Published 2018-07-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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
Quick Heal Total Security 64 bit 17.00 (QHTS64.exe), (QHTSFT64.exe) - Version 10.0.1.38; Quick Heal Total Security 32 bit 17.00 (QHTS32.exe), (QHTSFT32.exe) - Version 10.0.1.38; Quick Heal Internet Security 64 bit 17.00 (QHIS64.exe), (QHISFT64.exe) - Version 10.0.0.37; Quick Heal Internet Security 32 bit 17.00 (QHIS32.exe), (QHISFT32.exe) - Version 10.0.0.37; Quick Heal AntiVirus Pro 64 bit 17.00 (QHAV64.exe), (QHAVFT64.exe) - Version 10.0.0.37; and Quick Heal AntiVirus Pro 32 bit 17.00 (QHAV32.exe), (QHAVFT32.exe) - Version 10.0.0.37 allow DLL Hijacking because of Insecure Library Loading.

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

Quick Heal security products (Total Security, Internet Security, and AntiVirus Pro in versions 10.0.x) contain an Insecure Library Loading vulnerability allowing DLL Hijacking. The applications load DLLs from insecure paths, enabling a local attacker to execute arbitrary code by placing a malicious DLL in a location from which the vulnerable application loads libraries.

MitigationApply the vendor-supplied patch or update to Quick Heal products to a version that implements secure library loading with absolute paths and explicit DLL location specification.

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
Antivirus ProApplication
Affected:= 17.00
Internet SecurityApplication
Affected:= 17.00
Total SecurityApplication
Affected:= 17.00

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

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

  1. Verify Quick Heal product installation
    Check for Quick Heal Antivirus Pro, Internet Security, or Total Security in the system by reviewing installed programs list via Control Panel > Programs and Features, or by checking for Quick Heal folders in Program Files (e.g., C:\Program Files\Quick Heal\).
    Affected if Any Quick Heal product (Antivirus Pro, Internet Security, or Total Security) is installed on the system.
  2. Determine installed Quick Heal version
    Open the Quick Heal application and navigate to About/Help section to view the version number, or check the Windows registry key (typically under HKLM\SOFTWARE\Quick Heal\ or HKLM\SOFTWARE\WOW6432Node\Quick Heal) for the Version value.
    Affected if The installed version is exactly 17.00, matching the vulnerable version range.
  3. Observe DLL loading behavior for insecure paths
    Run the Quick Heal application while monitoring DLL loads using Process Monitor (procmon.exe) from Sysinternals. Configure a filter to show only process activity from the Quick Heal executable and look for DLL loads where the Path column shows relative or writable locations (e.g., current working directory, temp folders, or unquoted service paths).
    Affected if The application loads DLLs from paths that are writable by a local user (such as the application directory writable by non-admin users, or paths like %TEMP%).

A system is affected if Quick Heal Antivirus Pro, Internet Security, or Total Security version 17.00 is installed and the application loads DLLs from insecure or writable paths, enabling a local attacker to place a malicious DLL for execution.

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-supplied patch or update to Quick Heal products to a version that implements secure library loading with absolute paths and explicit DLL location specification.

Fix this in Antivirus Pro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-8090 — 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-2018-8090 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