# CVE-2010-1869: Memory corruption in n/a

> Attackers can execute arbitrary code by tricking users into opening a malicious PostScript file processed by GhostScript.

- **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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-1869, GHSA-gpcm-hmx8-j7h9

## What is CVE-2010-1869?

CVE-2010-1869 is a critical memory corruption vulnerability in n/a, published on 12 May 2010. 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

Stack-based buffer overflow in the parser function in GhostScript 8.70 and 8.64 allows context-dependent attackers to execute arbitrary code via a crafted PostScript file.

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

## Which versions are affected by CVE-2010-1869?

It affects 1 product.


Products: Artifex Gpl Ghostscript.

## How do I fix CVE-2010-1869?

Upgrade to a fixed version.

## Is CVE-2010-1869 being exploited?

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

Public exploit code:

- Ghostscript - '.PostScript' File Stack Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-4875](https://insights.sbomify.com/CVE-2012-4875/): Memory corruption in n/a (critical 9.3)
- [CVE-2010-1628](https://insights.sbomify.com/CVE-2010-1628/): Memory corruption in n/a (critical 9.3)
- [CVE-2016-9601](https://insights.sbomify.com/CVE-2016-9601/): Memory corruption in ghostscript (medium 5.3)
- [CVE-2013-6629](https://insights.sbomify.com/CVE-2013-6629/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1869 and fix it if it is affected.

What it is: CVE-2010-1869 is a critical memory corruption vulnerability in n/a, published on 12 May 2010. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-1869 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-2010-1869/ (Markdown: https://insights.sbomify.com/CVE-2010-1869/index.md)
```

## Sources

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

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