CVE-2017-8773
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 · uneditedQuick Heal Internet Security 10.1.0.316, Quick Heal Total Security 10.1.0.316, and Quick Heal AntiVirus Pro 10.1.0.316 are vulnerable to Out of Bounds Write on a Heap Buffer due to improper validation of dwCompressionSize of Microsoft WIM Header WIMHEADER_V1_PACKED. This vulnerability can be exploited to gain Remote Code Execution as well as Privilege Escalation.
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 confidenceQuick Heal security products (Internet Security, Total Security, and AntiVirus Pro v10.1.0.316) contain an out-of-bounds heap write vulnerability when parsing Microsoft WIM (Windows Imaging Format) files. The software fails to properly validate the dwCompressionSize field in the WIMHEADER_V1_PACKED structure, allowing an attacker to overflow the heap buffer and achieve remote code execution or 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 data<= 10.1.0.316<= 10.1.0.316<= 10.1.0.316CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 Quick Heal product is installedOpen Programs and Features (appwiz.cpl) or check the installation directory for Quick Heal (typically C:\Program Files\Quick Heal\) to confirm an installed product.Affected if No Quick Heal product is found, then this CVE does not apply.
-
Identify installed Quick Heal versionOpen the Quick Heal main interface, go to About or Help section, or check the registry key HKLM\SOFTWARE\Quick Heal\Core\Setup\Version to retrieve the exact version number.Affected if The version is 10.1.0.316 or lower.
-
Confirm product is an affected editionCheck the product name in Programs and Features or the Quick Heal interface - verify it is one of: Antivirus Pro, Internet Security, or Total Security.Affected if The product is Quick Heal Antivirus Pro, Internet Security, or Total Security at version <= 10.1.0.316.
-
Check if real-time or on-demand scanning is enabledOpen Quick Heal settings and verify that File System Shield, Email Protection, or Web Protection scanning is turned on, as these components process WIM files during scans.Affected if Scanning is enabled and the vulnerable WIM parsing code path can be triggered.
A system is affected if it has Quick Heal Antivirus Pro, Internet Security, or Total Security version 10.1.0.316 or lower with scanning functionality enabled.
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 dataOrganizations should immediately identify and update all systems running vulnerable Quick Heal versions (10.1.0.316) to the latest patched release. Until patches are applied, restrict processing of untrusted WIM files and monitor for indicators of compromise.
- 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-2017-8773 — 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-2017-8773 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