CVE-2014-0810
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 Sanshiro 2007 before update 3, 2008 before update 5, 2009 before update 6, and 2010 before update 6, and Sanshiro Viewer before 2.0.2.0, 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 confidenceThis is a code execution vulnerability in JustSystems Sanshiro (a Japanese word processing application) where specially crafted document files can trigger arbitrary code execution. The vulnerability is in unspecified parsing code within the software and requires user interaction (opening a malicious document) to exploit.
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= 2007= 2008= 2009= 2010= viewerCVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 JustSystems Sanshiro is installedLook for Sanshiro in the installed programs list via Control Panel > Programs and Features, or search for executable files named 'sanshiro.exe' or similar in Program Files directoriesAffected if Sanshiro is present on the system
-
Identify the installed Sanshiro versionRight-click the Sanshiro application shortcut or executable, select Properties, and check the Details tab for version information. Alternatively, open Sanshiro and go to Help > About to view version detailsAffected if Version matches 2007, 2008, 2009, 2010, or Viewer (any version in these product lines)
-
Confirm the Viewer component version if applicableIf the Viewer product is installed, check its version through the application properties or Help > About dialog. Look for version numbers below 2.0.2.0Affected if Viewer version is earlier than 2.0.2.0
-
Verify document interaction capabilityConfirm that the installed Sanshiro version can open document files (.sbk, .sab, or standard document formats used by Sanshiro) - this is the attack vector for this vulnerabilityAffected if The application can open documents and the version is within the affected ranges
The environment is affected if JustSystems Sanshiro version 2007, 2008, 2009, 2010, or Viewer (prior to 2.0.2.0) is installed and can open document files.
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 patches (Sanshiro 2007 update 3, 2008 update 5, 2009 update 6, 2010 update 6, or Viewer 2.0.2.0). Until patched, avoid opening documents from untrusted sources and consider application isolation.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0810 — 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-2014-0810 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