dbcve.org
Panda ActivescanApplication · Panda

CVE-2009-3735

HIGH · 9.3 CVSS v2.0 Published 2010-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 ActiveScan Installer ActiveX control in as2stubie.dll before 1.3.3.0 in PandaActiveScan Installer 2.0 in Panda ActiveScan downloads software in an as2guiie.cab archive located at an arbitrary URL, and does not verify the archive's digital signature before installation, which allows remote attackers to execute arbitrary code via a URL argument to an unspecified method.

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 Panda ActiveScan Installer ActiveX control (as2stubie.dll prior to version 1.3.3.0) downloads and installs software from a CAB archive at an attacker-specified URL without verifying digital signatures, allowing remote code execution.

MitigationDisable the vulnerable ActiveX control in Internet Explorer settings, remove the affected Panda ActiveScan 2.0 software, or apply the vendor patch to version 1.3.3.0 or later.

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:= 2.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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/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 if Panda ActiveScan 2.0 is installed
    Look for the software in Windows Add/Remove Programs, or search for Panda ActiveScan files in Program Files directories. Check registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Panda ActiveScan entries.
    Affected if Panda ActiveScan 2.0 is present on the system
  2. Locate and identify the as2stubie.dll file version
    Search for as2stubie.dll in the Panda ActiveScan installation directory (commonly in Program Files\Panda Software\ or similar). Right-click the file, select Properties, and view the Version tab to read the File Version.
    Affected if File version is lower than 1.3.3.0 or the file cannot be found with a version number at or above 1.3.3.0
  3. Check if the ActiveX control is registered in Internet Explorer
    Open Internet Explorer, go to Tools > Manage Add-ons, and look for 'Panda ActiveScan Installer' or as2stubie.dll in the list of ActiveX controls. Alternatively, check registry key HKEY_CLASSES_ROOT\CLSID for entries containing 'as2stubie' or 'ActiveScan'.
    Affected if The ActiveX control is listed and enabled in Internet Explorer add-ons
  4. Verify the installed Panda ActiveScan version number
    In Windows Add/Remove Programs, find Panda ActiveScan 2.0 and check the displayed version, or check the version info in the main executable or DLL files associated with the application.
    Affected if Version displayed is 2.0 without any patches applied

The system is affected if Panda ActiveScan 2.0 is installed and the as2stubie.dll file version is below 1.3.3.0 with the ActiveX control enabled in Internet Explorer.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable the vulnerable ActiveX control in Internet Explorer settings, remove the affected Panda ActiveScan 2.0 software, or apply the vendor patch to version 1.3.3.0 or later.

Recommended fix Moderate confidence

Panda ActiveScan Installer 1.3.3.0 or later (upgrade from 2.0 to the fixed 1.3.3.0+ release)

  1. 1. Verify current installation of Panda ActiveScan Installer 2.0 by checking the as2stubie.dll version in the system
  2. 2. Obtain Panda ActiveScan Installer version 1.3.3.0 or later from official Panda sources (pandasecurity.com)
  3. 3. Uninstall the existing vulnerable ActiveScan 2.0 installation
  4. 4. Install the updated version 1.3.3.0 or later which includes the digital signature verification fix
  5. 5. Verify the new as2stubie.dll version is 1.3.3.0 or higher
  6. 6. Confirm the ActiveX control now properly validates digital signatures before installation
Caveat Panda ActiveScan is a legacy product from 2009; verify current support status with Panda Security as the product may be discontinued or superseded by newer solutions

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

Fix this in Panda Activescan Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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