CVE-2008-3864 json
The ApiThread function in the firewall service (aka TmPfw.exe) in Trend Micro Network Security Component (NSC) modules, as used in Trend Mi…
published 2009-01-21 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-3850
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
The ApiThread function in the firewall service (aka TmPfw.exe) in Trend Micro Network Security Component (NSC) modules, as used in Trend Micro OfficeScan 8.0 SP1 Patch 1 and Internet Security 2007 and 2008 17.0.1224, allows remote attackers to cause a denial of service (service crash) via a packet with a large value in an unspecified size field.
Patch / fix
- securityfocus.com/bid/33358 patch
- secunia.com/advisories/33609 advisory
Exploit prediction
2.08% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
securityfocus.com
/bid/33358
vdb-entry, patch
-
secunia.com
/advisories/33609
third-party-advisory, patch, vendor-advisory
-
trendmicro.com
/ftp/documentation/readme/OSCE8.0_SP1_Patch1_CriticalPatch_3191_Readme.txt
vendor-advisory
-
secunia.com
/advisories/31160
third-party-advisory, vendor-advisory
-
securitytracker.com
/id?1021615
vdb-entry
- secunia.com /secunia_research/2008-42/
-
exchange.xforce.ibmcloud.com
/vulnerabilities/48106
vdb-entry
-
securityfocus.com
/archive/1/500195/100/0/threaded
mailing-list
-
vupen.com
/english/advisories/2009/0191
vdb-entry
-
securityreason.com
/securityalert/4937
third-party-advisory
-
securitytracker.com
/id?1021614
vdb-entry
Sources
- CVE List CVE-2008-3864
- NVD CVE-2008-3864
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.