# CVE-2017-1000159: Command injection in n/a

> Attackers can execute arbitrary commands via crafted filenames when printing to PDF in Evince, requiring users to update the application.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-1000159, DLA-1204-1, GHSA-vvj5-83p2-x3pp, MGASA-2017-0450, SUSE-SU-2018:0639-1, SUSE-SU-2018:0947-1, UBUNTU-CVE-2017-1000159, USN-3503-1

## What is CVE-2017-1000159?

CVE-2017-1000159 is a high-severity command injection vulnerability in n/a, published on 27 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Command injection in evince via filename when printing to PDF. This affects versions earlier than 3.25.91.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2017-1000159?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `evince` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 3.20.2-6.22.9 |
| `evince` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 2.28.2-0.7.3.1 |
| `evince` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 3.20.2-6.22.9 |
| `evince` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 2.28.2-0.7.3.1 |
| `evince` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 3.20.2-6.22.9 |
| `evince` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 2.28.2-0.7.3.1 |
| `evince` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 3.20.2-6.22.9 |
| `evince` | SUSE:Linux Enterprise Workstation Extension 12 SP3 | All versions | 3.20.2-6.22.9 |

Products: Gnome Evince.

## How do I fix CVE-2017-1000159?

Upgrade to a fixed version.

## Is CVE-2017-1000159 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-0433](https://insights.sbomify.com/CVE-2011-0433/): Memory corruption in n/a (medium 6.8)
- [CVE-2011-5244](https://insights.sbomify.com/CVE-2011-5244/): Integer overflow in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000159 and fix it if it is affected.

What it is: CVE-2017-1000159 is a high-severity command injection vulnerability in n/a, published on 27 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-1000159 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-2017-1000159/ (Markdown: https://insights.sbomify.com/CVE-2017-1000159/index.md)
```

## Sources

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

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