# CVE-2010-4820: Code injection in n/a

> Local attackers can execute arbitrary PostScript code by placing a malicious library file in the current working directory, affecting Ghostscript users.

- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** 27 Oct 2014
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-4820, GHSA-37q2-9vp4-q6f4

## What is CVE-2010-4820?

CVE-2010-4820 is a medium-severity code injection vulnerability in n/a, published on 27 Oct 2014. 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

Untrusted search path vulnerability in Ghostscript 8.62 allows local users to execute arbitrary PostScript code via a Trojan horse Postscript library file in Encoding/ under the current working directory, a different vulnerability than CVE-2010-2055.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Ghostscript Ghostscript.

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

Upgrade to a fixed version.

## Is CVE-2010-4820 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4270](https://insights.sbomify.com/CVE-2009-4270/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-0196](https://insights.sbomify.com/CVE-2009-0196/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-6725](https://insights.sbomify.com/CVE-2007-6725/): Memory corruption in n/a (high 7.5)
- [CVE-2008-0411](https://insights.sbomify.com/CVE-2008-0411/): Memory corruption in n/a (medium 6.8)
- [CVE-2008-6679](https://insights.sbomify.com/CVE-2008-6679/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-4820 is a medium-severity code injection vulnerability in n/a, published on 27 Oct 2014. 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-2010-4820 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-2010-4820/ (Markdown: https://insights.sbomify.com/CVE-2010-4820/index.md)
```

## Sources

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

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