CVE-2007-6436
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 · uneditedStack-based buffer overflow in JSGCI.DLL in JustSystems Ichitaro 2005, 2006, and 2007 allows user-assisted remote attackers to execute arbitrary code via a crafted document, as actively exploited in December 2007 by the Tarodrop.F trojan. NOTE: some of these details are obtained from third party information.
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 confidenceStack-based buffer overflow in JSGCI.DLL allows arbitrary code execution when a user opens a specially crafted Ichitaro document. The vulnerability affects JustSystems Ichitaro versions 2005, 2006, and 2007, and was actively exploited in the wild by the Tarodrop.F trojan in December 2007.
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= 2005= 2006= 2007CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify if Ichitaro is installedCheck for the presence of Ichitaro in the program files directory (commonly C:\Program Files\JustSystems\Ichitaro\) or look for Ichitaro in the list of installed programs via Control Panel > Programs and Features.Affected if Ichitaro is found on the system
-
Identify the installed Ichitaro versionRight-click the Ichitaro executable (usually ichitaro.exe or a similar .exe in the Ichitaro folder), select Properties, and check the Version tab for the product version number.Affected if The version number shown is 2005, 2006, or 2007
-
Locate the JSGCI.DLL componentSearch for the file JSGCI.DLL within the Ichitaro installation directory (typically in C:\Program Files\JustSystem\Ichitaro\ or a version-specific subfolder).Affected if JSGCI.DLL exists in the Ichitaro installation folder
-
Confirm the DLL version matches affected releasesRight-click JSGCI.DLL, select Properties, and check the Version tab to compare the file version against what shipped with Ichitaro 2005, 2006, or 2007.Affected if The DLL version corresponds to one of the affected Ichitaro versions (2005, 2006, or 2007)
A system is affected if it has Ichitaro version 2005, 2006, or 2007 installed with the vulnerable JSGCI.DLL component present.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUsers should avoid opening untrusted Ichitaro documents; organizations should identify and remove or upgrade affected Ichitaro installations since these legacy versions are likely end-of-life with no vendor patches available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-6436 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-6436 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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