# CVE-2013-3934: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a malicious WPS file with a long font name in Kingsoft Writer.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 10 Sep 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-w589-3w29-h2mg

## What is CVE-2013-3934?

CVE-2013-3934 is a critical memory corruption vulnerability in n/a, published on 10 Sep 2013. 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

Stack-based buffer overflow in Kingsoft Writer 2012 8.1.0.3030, as used in Kingsoft Office 2013 before 9.1.0.4256, allows remote attackers to execute arbitrary code via a long font name in a WPS file.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2013-3934?

It affects 2 products.


Products: Kingsoft Office 2012, Kingsoft Writer 2012.

## How do I fix CVE-2013-3934?

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

## Is CVE-2013-3934 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-3934 exists.

Public exploit code:

- Kingsoft Office Writer 2012 8.1.0.3385 - '.wps' Local Buffer Overflow (SEH) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-4886](https://insights.sbomify.com/CVE-2012-4886/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-3934 and fix it if it is affected.

What it is: CVE-2013-3934 is a critical memory corruption vulnerability in n/a, published on 10 Sep 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-3934 exists.

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-2013-3934/ (Markdown: https://insights.sbomify.com/CVE-2013-3934/index.md)
```

## Sources

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

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