CVE-2017-2789
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 · uneditedWhen copying filedata into a buffer, JustSystems Ichitaro Office 2016 Trial will calculate two values to determine how much data to copy from the document. If both of these values are larger than the size of the buffer, the application will choose the smaller of the two and trust it to copy data from the file. This value is larger than the buffer size, which leads to a heap-based buffer overflow. This overflow corrupts an offset in the heap used in pointer arithmetic for writing data and can lead to code execution under the context of the application.
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 confidenceHeap-based buffer overflow in JustSystems Ichitaro Office 2016 Trial when copying file data. The application calculates two values to determine copy size, and when both exceed the buffer size, it incorrectly selects the smaller value which remains larger than the buffer, causing overflow that corrupts heap offsets used in pointer arithmetic and can lead to code execution.
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 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 Ichitaro Office installationOpen Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed software. Look for any JustSystems Ichitaro entry.Affected if JustSystems Ichitaro Office 2016 Trial appears in the installed programs list
-
Identify exact version numberIf Ichitaro is installed, locate its executable (typically in C:\Program Files\JustSystems\Ichitaro\ or C:\Program Files (x86)\JustSystems\Ichitaro\). Right-click the main executable (e.g., ichitaro.exe) and select Properties > Details to view the File Version.Affected if The displayed version falls within or below the 2016 release cycle (versions prior to vendor patch availability)
-
Determine if Trial versionLaunch Ichitaro and check the title bar or Help > About dialog for 'Trial', 'Evaluation', or '体験版' (Japanese for Trial) indicators. Alternatively, check the program folder for files named 'trial' or 'eval' in the filename.Affected if The installed version is identified as a Trial or Evaluation copy
-
Verify vulnerable component existsInspect the Ichitaro program directory for the file handling module responsible for copy operations. The vulnerability exists in the code that handles copying file data into buffers. No specific file name is publicly disclosed; presence of the main ichitaro.exe application indicates the vulnerable code path exists.Affected if The main Ichitaro application executable is present, indicating the vulnerable copy operation code is included
A user is affected if JustSystems Ichitaro Office 2016 Trial (or any unpatched Ichitaro version) is installed on the system.
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 dataApply vendor patch when released. Until then, restrict or disable use of Ichitaro Office 2016 Trial, implement application sandboxing, or use alternative office software to eliminate the attack vector.
- Consultation2.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2789 — 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-2017-2789 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