# CVE-2018-6217: Denial of service in n/a

> Remote attackers can crash Kingsoft WPS Office via crafted web pages, documents, or RTF files, requiring users to update the software.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3gf7-6hqc-m4jp

## What is CVE-2018-6217?

CVE-2018-6217 is a medium-severity denial of service vulnerability in n/a, published on 25 Jan 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The WStr::_alloc_iostr_data() function in kso.dll in Kingsoft WPS Office 10.1.0.7106 and 10.2.0.5978 allows remote attackers to cause a denial of service (application crash) via a crafted (a) web page, (b) office document, or (c) .rtf file.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-6217?

It affects 1 product.


Products: Kingsoftstore Kingsoft Wps Office.

## How do I fix CVE-2018-6217?

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

## Is CVE-2018-6217 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6217 and fix it if it is affected.

What it is: CVE-2018-6217 is a medium-severity denial of service vulnerability in n/a, published on 25 Jan 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-6217 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-2018-6217/ (Markdown: https://insights.sbomify.com/CVE-2018-6217/index.md)
```

## Sources

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

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