# CVE-2015-2810: Integer overflow in n/a

> Remote attackers can cause denial of service or potentially execute code via a crafted document with a large paragraph size in Hancom Office HanWord.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 May 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3f8r-37x3-r4g8

## What is CVE-2015-2810?

CVE-2015-2810 is a high-severity vulnerability in n/a, published on 15 May 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Integer 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.

Weakness: CWE-189

## Which versions are affected by CVE-2015-2810?

It affects 4 products.


Products: Hancom Hanword Viewer 2007, Hancom Hanword Viewer 2010, Hancom Hwp 2014, Hancom Hwpviewer 2014.

## How do I fix CVE-2015-2810?

No fix has been published for CVE-2015-2810 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-2810 being exploited?

There is no known exploitation of CVE-2015-2810 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2810 and fix it if it is affected.

What it is: CVE-2015-2810 is a high-severity vulnerability in n/a, published on 15 May 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-2810 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-2810/ (Markdown: https://insights.sbomify.com/CVE-2015-2810/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-2810
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-2810
- OSV: https://osv.dev/vulnerability/CVE-2015-2810

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-2810/
Summaries are generated and may contain mistakes; the official description above is the record.