CVE-2015-2810
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 · uneditedInteger overflow in the HwpApp::CHncSDS_Manager function in Hancom Office HanWord processor, as used in Hwp 2014 VP before 9.1.0.2342, HanWord Viewer 2007 and Viewer 2010 8.5.6.1158, and HwpViewer 2014 VP 9.1.0.2186, allows remote attackers to cause a denial of service (crash) and possibly "influence the program's execution flow" via a document with a large paragraph size, which triggers heap corruption.
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 confidenceInteger overflow in HwpApp::CHncSDS_Manager function in Hancom Office HanWord processor when parsing documents with large paragraph sizes, leading to heap corruption. This can cause denial of service (crash) and potentially allow attackers to influence program execution flow.
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 versions= 8.5.6.1158<= 9.1.0.2342= 9.1.0.2186CVSS 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.
-
Identify if Hancom Office software is installedCheck system for Hancom HanWord, Hwp, or HwpViewer applications. Look in Program Files for 'Hancom' folder or check installed programs list.Affected if Any Hancom Office suite is installed
-
Determine installed Hancom HanWord versionOpen the HanWord/Hwp application and navigate to Help > About, or right-click the executable and view Properties > Details for version information.Affected if Version cannot be determined but Hancom software is present
-
Check Hanword Viewer 2007 versionIf using Hanword Viewer 2007, any version is affected since all versions are vulnerable.Affected if Hanword Viewer 2007 is installed (all versions)
-
Check Hanword Viewer 2010 versionIf using Hanword Viewer 2010, verify version equals 8.5.6.1158 specifically.Affected if Version is exactly 8.5.6.1158
-
Check Hwp 2014 versionIf using Hwp 2014, verify version is 9.1.0.2342 or lower.Affected if Version is 9.1.0.2342 or any lower version
-
Check Hwpviewer 2014 versionIf using Hwpviewer 2014, verify version equals 9.1.0.2186 specifically.Affected if Version is exactly 9.1.0.2186
User is affected if Hancom HanWord or Hwp software is installed and the version matches one of the affected versions: any Hanword Viewer 2007, version 8.5.6.1150, version 8.5.6.1158, Hwp 2014 at 9.1.0.2342 or below, or Hwpviewer 2014 at version 9.1.0.2186.
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 dataUpdate to Hancom Office Hwp 2014 VP version 9.1.0.2342 or later; avoid opening untrusted or unverified HWP documents from unknown sources.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2810 — 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-2015-2810 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