dbcve.org
IchitaroApplication · Justsystems

CVE-2014-7247

HIGH · 10.0 CVSS v2.0 Published 2014-11-26
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
Unspecified vulnerability in JustSystems Ichitaro 2008 through 2011; Ichitaro Government 6, 7, 2008, 2009, and 2010; Ichitaro Pro; Ichitaro Pro 2; Ichitaro 2011 Sou; Ichitaro 2012 Shou; Ichitaro 2013 Gen; and Ichitaro 2014 Tetsu allows remote attackers to execute arbitrary code via a crafted file.

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 confidence

A critical arbitrary code execution vulnerability in JustSystems Ichitaro Japanese word processor versions 2008-2014 allows remote attackers to execute arbitrary code via a crafted file. The specific vulnerability type is unspecified in available sources, but the CVSS 10 score indicates trivial exploitation likely requiring only file opening by the victim.

MitigationDo not open untrusted or unexpected Ichitaro document files from unknown sources. Apply vendor patches or update to the latest supported version of Ichitaro when released.

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
IchitaroApplication
Affected:= 6= 7= 2008= 2009= 2010= 2011= 2012= 2013= 2014
Ichitaro ProApplication
Affected:all versions= 2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Ichitaro installation directory
    Search common installation paths on Windows systems (e.g., C:\Program Files\JustSystems or C:\Program Files (x86)\JustSystems) or use system search to find 'ichitaro.exe' or similar executable files.
    Affected if Ichitaro executable is found on the system
  2. Identify installed Ichitaro version
    Check the file properties of the main Ichitaro executable (typically ichitaro.exe or similar), or look in Windows Registry under HKLM\SOFTWARE\JustSystems\Ichitaro for version information.
    Affected if Version matches 6, 7, 2008, 2009, 2010, 2011, 2012, 2013, 2014, or any Pro version (including version 2)
  3. Confirm Ichitaro Pro installation
    Search for 'Ichitaro Pro' or 'JSPF' related executables and check their version information via file properties or registry keys.
    Affected if Any version of Ichitaro Pro is installed
  4. Check for document file associations
    Examine Windows Registry under HKCR\.jtd or similar extensions to see if Ichitaro document types (.jtd, .jtt, etc.) are registered as handlers for the installed Ichitaro version.
    Affected if Ichitaro document file types are associated with an affected version

A system is affected if JustSystems Ichitaro (versions 6, 7, 2008-2014) or Ichitaro Pro (any version including v2) is installed and handles document files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.justsystems.com →
Interim mitigation

Do not open untrusted or unexpected Ichitaro document files from unknown sources. Apply vendor patches or update to the latest supported version of Ichitaro when released.

Recommended fix Moderate confidence

Apply the JustSystems patch from js14003 - specific version numbers not determinable from provided information

  1. 1. Visit the JustSystems vendor patch page at http://www.justsystems.com/jp/info/js14003.html to obtain the official patch
  2. 2. Download the patch corresponding to your specific Ichitaro product version (6, 7, 2008, 2009, Pro, Pro 2, or later versions including 2010-2014)
  3. 3. Apply the patch following the vendor's installation instructions
  4. 4. Verify the patch was successfully applied by checking the software version or running the application

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ichitaro Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-7247 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-7247 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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