CVE-2017-2790
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 processing a record type of 0x3c from a Workbook stream from an Excel file (.xls), JustSystems Ichitaro Office trusts that the size is greater than zero, subtracts one from the length, and uses this result as the size for a memcpy. This results in a heap-based buffer overflow 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 confidenceJustSystems Ichitaro Office contains a heap-based buffer overflow vulnerability when processing Excel (.xls) Workbook streams. When handling record type 0x3c, the application subtracts one from the record length and uses this value as the size parameter for memcpy without validating that the length is greater than zero, resulting in heap corruption and potential code execution under the application context.
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 if JustSystems Ichitaro is installedCheck installed programs list or look for ichitaro.exe executable on the system. Common installation paths may include C:\Program Files\JustSystems\ or C:\Program Files (x86)\JustSystems\Affected if Ichitaro software is found on the system
-
Identify the installed version of IchitaroRight-click on the Ichitaro application in the Start menu or installed programs list to view version information, or check the executable properties if locatedAffected if Any version of JustSystems Ichitaro is installed (all versions are affected)
-
Verify Excel file handling capabilityCheck if Ichitaro is configured to open or can open .xls file extensions. Attempt to open a sample .xls file with Ichitaro or check file association settings for .xls filesAffected if Ichitaro is associated with or can process .xls Excel files
-
Determine exposure to untrusted .xls filesReview whether the system user or workflow involves opening Excel files from external or untrusted sources using Ichitaro. Check browser download folders, email attachments, or shared network locations that may contain .xls files opened by IchitaroAffected if Ichitaro is used to open .xls files from potentially untrusted sources
If JustSystems Ichitaro is installed and can process Excel (.xls) files, the system is affected by this vulnerability since all versions contain the heap overflow flaw in Workbook stream handling.
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 dataAvoid opening untrusted or unknown Excel (.xls) files in Ichitaro Office until a vendor patch is available. Consider using alternative office productivity software for handling legacy Excel files.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2790 — 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-2790 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