# CVE-2018-3975: Memory corruption in Atlantis Word Processor

> A specially crafted RTF file can trigger an out-of-bounds write via an uninitialized variable, potentially allowing arbitrary code execution.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 1 Oct 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6wh2-mpvp-28q3

## What is CVE-2018-3975?

CVE-2018-3975 is a high-severity memory corruption vulnerability in The Atlantis Word Processor Team Atlantis Word Processor, published on 1 Oct 2018. 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

An exploitable uninitialized variable vulnerability exists in the RTF-parsing functionality of Atlantis Word Processor 3.2.6 version. A specially crafted RTF file can leverage an uninitialized stack address, resulting in an out-of-bounds write, which in turn could lead to code execution.

Weakness: CWE-908 (Use of Uninitialized Resource)

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

It affects 1 product.


Products: Atlantiswordprocessor Atlantis Word Processor.

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

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

## Is CVE-2018-3975 being exploited?

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

## Other vulnerabilities in The Atlantis Word Processor Team Atlantis Word Processor

- [CVE-2018-3983](https://insights.sbomify.com/CVE-2018-3983/): Memory corruption in Atlantis Word Processor (high 8.8)
- [CVE-2018-4038](https://insights.sbomify.com/CVE-2018-4038/): Memory corruption in Atlantis Word Processor (high 8.8)
- [CVE-2018-4039](https://insights.sbomify.com/CVE-2018-4039/): Memory corruption in Atlantis Word Processor (high 8.8)
- [CVE-2018-4040](https://insights.sbomify.com/CVE-2018-4040/): Null dereference in Atlantis Word Processor (high 8.8)
- [CVE-2018-3978](https://insights.sbomify.com/CVE-2018-3978/): Memory corruption in Atlantis Word Processor (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-3975 is a high-severity memory corruption vulnerability in The Atlantis Word Processor Team Atlantis Word Processor, published on 1 Oct 2018. 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-2018-3975 in the wild and no public exploit code.

Affected product: The Atlantis Word Processor Team Atlantis Word Processor. 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-3975/ (Markdown: https://insights.sbomify.com/CVE-2018-3975/index.md)
```

## Sources

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

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