Antivirus Plus 2009Application · Quickheal

CVE-2009-4556

HIGH · 7.2 CVSS v2.0 Published 2010-01-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
No privileges 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
Quick Heal AntiVirus Plus 2009 10.00 SP1 and Quick Heal Total Security 2009 10.00 SP1 use weak permissions (Everyone: Full Control) for the product files, which allows local users to gain privileges by replacing executables with Trojan horse programs, as demonstrated by replacing quhlpsvc.exe.

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 AntiVirus Plus 2009 and Total Security 2009 install product files with weak permissions, granting the 'Everyone' group Full Control access. Local users can replace legitimate executables (such as quhlpsvc.exe) with malicious code, achieving privilege escalation when the replaced file is executed.

MitigationRestrict file permissions on the Quick Heal product directory to remove 'Everyone: Full Control' and assign restrictive permissions to authorized administrators and the SYSTEM account only.

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 Plus 2009Application
Affected:= 10.00
Total Security 2009Application
Affected:= 10.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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:N/C:C/I:C/A:C

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 if Quick Heal 2009 is installed
    Check Add/Remove Programs or look for Quick Heal installation in C:\Program Files\Quick Heal. Verify the version number displayed is 10.00
    Affected if Quick Heal Antivirus Plus 2009 or Total Security 2009 version 10.00 is installed
  2. Locate the Quick Heal installation directory
    Common paths include C:\Program Files\Quick Heal\ or C:\Program Files\Quick Heal AntiVirus\. Check the specific product subfolder such as 'AntiVirus Plus 2009' or 'Total Security 2009'
    Affected if The product installation directory exists on the system
  3. Check file permissions on the Quick Heal program directory
    Right-click the Quick Heal installation folder, go to Properties > Security tab. Examine the permissions listed for each group or user. Alternatively, run 'icacls "C:\Program Files\Quick Heal"' from an elevated command prompt
    Affected if The 'Everyone' group appears in the list of allowed users/groups for the directory
  4. Verify Everyone group has Full Control permissions
    In the Security tab, select the Everyone group and click 'Edit' to view permissions. Check if the 'Full Control' checkbox under 'Allow' is ticked, or run 'icacls "C:\Program Files\Quick Heal" | findstr Everyone' to see the granted permissions
    Affected if The Everyone group is granted Full Control permissions (allows full read, write, and execute access)
  5. Check permissions on critical executable files
    Inspect permissions on key executables such as quhlpsvc.exe in the installation directory. Run 'icacls "C:\Program Files\Quick Heal\...\quhlpsvc.exe"' or check via the Security tab
    Affected if The Everyone group has Full Control on executable files within the Quick Heal directory

A user is affected if Quick Heal AntiVirus Plus 2009 or Total Security 2009 version 10.00 is installed and the Everyone group has Full Control permissions on the installation directory or its executables.

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

Restrict file permissions on the Quick Heal product directory to remove 'Everyone: Full Control' and assign restrictive permissions to authorized administrators and the SYSTEM account only.

Fix this in Antivirus Plus 2009 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2009-4556 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2009-4556 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