Panda ActivescanApplication · Panda

CVE-2005-3922

HIGH · 7.5 CVSS v2.0 Published 2005-11-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Heap-based buffer overflow in pskcmp.dll in Panda Software Antivirus library allows remote attackers to execute arbitrary code via a crafted ZOO 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

Heap-based buffer overflow in pskcmp.dll, a Panda Software Antivirus library component, allows remote code execution when the antivirus scans a specially crafted ZOO archive file. The overflow occurs in heap memory during archive parsing, enabling attackers to inject and execute arbitrary code.

MitigationUpdate Panda Software Antivirus to a version that patches this vulnerability, or if unsupported, replace with a current antivirus solution and implement email/gateway filtering to block ZOO archive attachments.

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
Panda ActivescanApplication
Affected:= 5.0
Panda AntivirusApplication
Affected:= 2.0
Panda Antivirus PlatinumApplication
Affected:= 2.0
Panda Businessecure AntivirusApplication
Affected:all versions
Panda Clientshield With Truprevent TechnologiesApplication
Affected:all versions
Panda Enterprisecure With Truprevent TechnologiesApplication
Affected:all versions
Panda ExchangesecureApplication
Affected:all versions
Panda FilesecureApplication
Affected:all versions

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
Partial
Integrity
Partial
Availability
Partial

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

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 installed Panda antivirus product
    Check Add/Remove Programs or program files directory for Panda Software antivirus installations (look for Panda Activescan, Panda Antivirus, Panda Antivirus Platinum, Panda Businessecure Antivirus, Panda Clientshield, Panda Enterprisecure, Panda Exchangesecure, or Panda Filesecure)
    Affected if Any of the listed Panda products are installed (versions 5.0 or lower for Activescan, 2.0 or lower for Antivirus/Platinum, or any version for Businessecure/Clientshield/Enterprisecure/Exchangesecure/Filesecure)
  2. Verify product version number
    Locate the installed Panda product in program files, check version info in the executable or DLL properties, or run 'reg query' for the product version in Windows Registry under HKLM\SOFTWARE\Panda Software
    Affected if Version is 5.0 or lower for Activescan, 2.0 or lower for Antivirus or Platinum, or any version for the all-versions products listed
  3. Confirm pskcmp.dll exists
    Search for pskcmp.dll in the Panda installation directory (commonly C:\Program Files\Panda Software or subdirectories)
    Affected if The vulnerable DLL file pskcmp.dll is present in the Panda installation folder
  4. Check if ZOO archive scanning is enabled
    Open Panda antivirus configuration and look for archive scanning settings; verify if ZOO archive format support is enabled in the scan settings
    Affected if ZOO archive scanning/parsing is enabled in the antivirus configuration

A user is affected if any of the listed Panda products are installed with a version matching the affected ranges AND the pskcmp.dll component exists AND ZOO archive scanning is enabled, allowing the specially crafted ZOO file to trigger the heap overflow during antivirus scanning.

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

Update Panda Software Antivirus to a version that patches this vulnerability, or if unsupported, replace with a current antivirus solution and implement email/gateway filtering to block ZOO archive attachments.

Fix this in Panda Activescan Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
11.0 hours of engineering $2,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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