CVE-2009-4737 json
Stack-based buffer overflow in JustSystems Corporation Ichitaro 13, 2004 through 2009, Viewer 2009 19.0.1.0 and earlier, and other versions…
published 16y ago modified 4mo ago also EUVD-2009-4701
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.5%
- EPSS 3.5% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
Stack-based buffer overflow in JustSystems Corporation Ichitaro 13, 2004 through 2009, Viewer 2009 19.0.1.0 and earlier, and other versions allows context-dependent attackers to execute arbitrary code via a crafted Rich Text File (RTF), related to "pvpara ffooter."
Patch / fix
- vupen.com/english/advisories/2009/0957 advisory
- justsystems.com/jp/info/js09002.html advisory
Is CVE-2009-4737 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
3.48% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
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
-
vupen.com
/english/advisories/2009/0957
vdb-entry, patch, vendor-advisory
-
justsystems.com
/jp/info/js09002.html
patch, vendor-advisory
-
secunia.com
/advisories/34611
third-party-advisory, vendor-advisory
-
osvdb.org
/53349
vdb-entry
-
securityfocus.com
/bid/34403
vdb-entry
-
jvndb.jvn.jp
/ja/contents/2009/JVNDB-2009-000018.html
third-party-advisory
- fourteenforty.jp /research/advisory.cgi?FFRRA-20090407
- ipa.go.jp /security/vuln/documents/2009/200904_ichitaro.html
-
exchange.xforce.ibmcloud.com
/vulnerabilities/49739
vdb-entry
-
jvn.jp
/en/jp/JVN33846134/index.html
third-party-advisory
Sources
- CVE List CVE-2009-4737
- NVD CVE-2009-4737
Fencer Intel 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.