CVE-2006-0807 json
Stack-based buffer overflow in NJStar Chinese and Japanese Word Processor 4.x and 5.x before 5.10 allows user-assisted attackers to execute…
published 2006-02-21 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-0813
- cvss
- 5.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.0%
- EPSS 4.0% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
Stack-based buffer overflow in NJStar Chinese and Japanese Word Processor 4.x and 5.x before 5.10 allows user-assisted attackers to execute arbitrary code via font names in NJStar (.njx) documents.
Patch / fix
- secunia.com/advisories/18702 advisory
- secunia.com/secunia_research/2006-5/advisory/ advisory
Exploit prediction
3.95% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- secunia.com http://secunia.com/secunia_research/2006-5/advisory/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.1 | AV:N/AC:H/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
secunia.com
/advisories/18702
third-party-advisory, patch, vendor-advisory
-
secunia.com
/secunia_research/2006-5/advisory/
exploit, patch, vendor-advisory
-
vupen.com
/english/advisories/2006/0670
vdb-entry, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/24773
vdb-entry
- njstar.com /njstar/chinese/
-
securityreason.com
/securityalert/461
third-party-advisory
- njstar.com /njstar/japanese/
-
securityfocus.com
/bid/16737
vdb-entry
-
osvdb.org
/23354
vdb-entry
-
securityfocus.com
/archive/1/425498/100/0/threaded
mailing-list
-
securitytracker.com
/id?1015649
vdb-entry
Sources
- CVE List CVE-2006-0807
- NVD CVE-2006-0807
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.