CVE-2008-3155 json
Stack-based buffer overflow in the ActiveX control (as2guiie.dll) in Panda ActiveScan before 1.02.00 allows remote attackers to cause a den…
published 2008-07-11 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-3145
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.7%
- EPSS 7.7% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
Stack-based buffer overflow in the ActiveX control (as2guiie.dll) in Panda ActiveScan before 1.02.00 allows remote attackers to cause a denial of service (crash) or execute arbitrary code via a long argument to the Update method.
Timeline
- First public exploit (EDB-6004)
- Published
Exploit prediction
7.71% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-6004 Panda Security ActiveScan 2.0 (Update) - Remote Buffer Overflow remote, 2008-07-04
- karol.wiesek.pl http://karol.wiesek.pl/files/panda.tgz referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
exploit-db.com
/exploits/6004
exploit
-
karol.wiesek.pl
/files/panda.tgz
exploit
-
secunia.com
/advisories/30841
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/43588
vdb-entry
-
vupen.com
/english/advisories/2008/2008/references
vdb-entry
-
securityfocus.com
/bid/30086
vdb-entry
-
lists.grok.org.uk
/pipermail/full-disclosure/2008-July/063061.html
mailing-list
-
lists.grok.org.uk
/pipermail/full-disclosure/2008-July/063068.html
mailing-list
-
securitytracker.com
/id?1020432
vdb-entry
Sources
- CVE List CVE-2008-3155
- NVD CVE-2008-3155
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.