dbcve.org
Avg Anti VirusApplication · Avg

CVE-2009-1784

HIGH · 10.0 CVSS v2.0 Published 2009-05-22
Fix available
A fix is available. Upgrade to after 8.0.156 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
The AVG parsing engine 8.5 323, as used in multiple AVG anti-virus products including Anti-Virus Network Edition, Internet Security Netzwerk Edition, Server Edition für Linux/FreeBSD, Anti-Virus SBS Edition, and others allows remote attackers to bypass malware detection via a crafted (1) RAR and (2) ZIP archive.

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

The AVG parsing engine 8.5.323 fails to properly scan crafted RAR and ZIP archives, allowing embedded malware to bypass detection. Attackers can deliver malicious payloads by sending specially constructed archive files that the antivirus fails to unpack or analyze correctly.

MitigationUpdate AVG anti-virus products to a patched version that resolves the archive parsing vulnerability. Verify that the updated version properly scans RAR and ZIP archives.

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
Avg Anti VirusApplication
Affected:<= 8.0.156= 6.0.710= 7.0= 7.0.251= 7.0.323= 7.1.308= 7.1.407= 7.5.51= 7.5.448= 7.5.476= 8.0

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
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/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. Check installed AVG AntiVirus version
    Open AVG interface, go to Help > About, or run 'avgui' from command line and navigate to the version information section. On Windows, you can also check in Control Panel > Programs and Features > AVG AntiVirus > Version
    Affected if The version matches any of these: 6.0.710, 7.0, 7.0.251, 7.0.323, 7.1.308, 7.1.407, 7.5.51, 7.5.448, 7.5.476, 8.0, or is 8.0.156 or lower
  2. Verify archive scanning component is enabled
    Open AVG settings > Shields > Archive Scanner, or access through the main interface: Settings > Protection > Archive Scanner. Confirm the scanner is turned ON
    Affected if Archive scanning is enabled and the AVG version matches the affected versions listed above
  3. Confirm RAR and ZIP archive handling
    In AVG settings, navigate to Scanner Settings or Advanced Settings > Archive. Verify if RAR and ZIP archives are set to be scanned. Check if there are any known exceptions or exclusions for archive types
    Affected if RAR and ZIP archive scanning is active on a vulnerable version of AVG
  4. Check parsing engine version if exposed
    In AVG interface, look for Details or Technical Information section that may show the engine/definition version (such as 8.5.323 mentioned for this vulnerability). This may be visible in logs or about screen
    Affected if The parsing engine version shown is 8.5.323 specifically

You are affected if your AVG AntiVirus version matches any of the listed affected versions (6.0.710 through 8.0.156) AND you have archive scanning enabled for RAR/ZIP files.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 8.0.156
Interim mitigation

Update AVG anti-virus products to a patched version that resolves the archive parsing vulnerability. Verify that the updated version properly scans RAR and ZIP archives.

Recommended fix Moderate confidence

Latest supported AVG Anti-Virus version (modern version post-8.0)

  1. Identify the current AVG Anti-Virus version installed on affected systems
  2. Confirm the exact version number matches one of the affected releases: <= 8.0.156, 6.0.710, 7.0, or 7.0.251
  3. Contact AVG customer support or visit the official AVG website to obtain the latest supported version for your product line
  4. Download and install the latest AVG anti-virus product version from the official vendor source
  5. Verify the new version is running and update virus definition databases
  6. Test that RAR and ZIP archive scanning functions correctly with the new version
Caveat Old AVG 6.0/7.0 installations may require fresh installation rather than upgrade; legacy system compatibility should be verified before migration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Avg Anti Virus Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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