CVE-2013-3644
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 2006 through 2013; Ichitaro Pro through 2; Ichitaro Government 6, 7, and 2006 through 2010; Ichitaro Portable with oreplug; Ichitaro Viewer; and Ichitaro JUST School through 2010 allows remote attackers to execute arbitrary code via a crafted document.
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 confidenceArbitrary code execution vulnerability in JustSystems Ichitaro word processing software. Attackers can execute malicious code by enticing users to open specially crafted document files. The vulnerability is in the document parsing functionality and requires no authentication or user interaction beyond opening the file.
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= 6= 7= 2006= 2007= 2008= 2009= 2010= 2011= 2012= 2013all versionsall versionsall versionsCVSS 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
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/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.
-
Check if any Ichitaro product is installedLook for Ichitaro in installed programs via Windows Control Panel > Programs and Features, or search for ichitaro.exe in common installation directories such as C:\Program Files\JustSystems or C:\Program Files (x86)\JustSystemsAffected if Any Ichitaro application (Ichitaro, Ichitaro Just School, Ichitaro Portable, or Ichitaro Viewer) is found on the system
-
Identify the exact version of installed IchitaroRight-click on the Ichitaro executable (typically ichitaro.exe) in the installation folder, select Properties, and check the Version tab. Alternatively, open Ichitaro and go to Help > Version InformationAffected if The version displayed is 6, 7, 2006, 2007, 2008, 2009, 2010, 2011, 2012, or 2013, or if the product is Ichitaro Just School, Portable, or Viewer (any version)
-
Confirm document parsing functionality is enabledVerify the Ichitaro application can open .jut, .doc, or other document files. The vulnerability triggers when the document parsing module processes a specially crafted fileAffected if The application can open and parse document files
The environment is affected if JustSystems Ichitaro (versions 6-2013), Ichitaro Just School, Ichitaro Portable, or Ichitaro Viewer is installed and capable of opening documents
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 documents from untrusted or unknown sources. Consider upgrading to supported versions if available, or implement application whitelisting and endpoint protection to block execution of malicious files.
- Consultation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3644 — 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-2013-3644 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