CVE-2010-3915
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 · uneditedUnspecified vulnerability in JustSystems Ichitaro and Ichitaro Government allows remote attackers to execute arbitrary code via a crafted document, a different vulnerability than CVE-2010-3916.
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 · moderate confidenceA remote code execution vulnerability in JustSystems Ichitaro and Ichitaro Government word processors allows attackers to execute arbitrary code by tricking users into opening specially crafted document files. The vulnerability is triggered through parsing of malicious Ichitaro (.ITD, .IOD, etc.) documents and requires no authentication.
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 dataall versions= 2007= 2008= 2009CVSS 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.
-
Confirm JustSystems Ichitaro installationLook for Ichitaro executable in typical installation paths such as C:\Program Files\JustSystems\Ichitaro\ or check Windows Program Files folder for JustSystems directory. On Windows, also check Add/Remove Programs or Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' for Ichitaro entry.Affected if JustSystems Ichitaro or Ichitaro Government is present on the system
-
Identify installed Ichitaro versionRight-click the Ichitaro executable (usually itaruXX.exe where XX is version number) and select Properties, or open Ichitaro and check Help > Version Information menu.Affected if Installed version matches 2007, 2008, 2009 or any version (all versions are affected per vendor advisory)
-
Verify vulnerable file type associationsCheck Windows Registry under HKCR\.ITD and HKCR\.IOD keys to see if these extensions are associated with Ichitaro application, or check File Type settings within Ichitaro.Affected if File types .ITD, .IOD, or other Ichitaro document formats are associated with the application (required for exploitation)
-
Inspect document parsing componentVerify that the Ichitaro document parsing library (typically located in the application directory) is present and not renamed or removed.Affected if Document parsing component exists and is enabled (this component processes the vulnerable .ITD/.IOD formats)
User is affected if JustSystems Ichitaro or Ichitaro Government is installed with any version and the application processes .ITD, .IOD or related document formats.
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 dataDo not open untrusted or unexpected Ichitaro documents from unknown sources. Apply vendor patches when available. Consider disabling file preview features and deploying application sandboxing or endpoint protection to mitigate document-based attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3915 — 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-2010-3915 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