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

> Remote attackers can execute arbitrary commands by tricking users into opening a malicious .cbt file in Evince.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:** Yes
- **Published:** 5 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** CLEANSTART-2024-SE84870, DEBIAN-CVE-2017-1000083, DLA-1031-1, DSA-3911-1, DSA-3916-1, GHSA-c796-cmwx-5c79, MGASA-2017-0244, MGASA-2017-0251, RHSA-2017:2388, SUSE-SU-2017:1893-1, SUSE-SU-2017:1894-1, SUSE-SU-2017:2390-1, SUSE-SU-2017:3428-1, UBUNTU-CVE-2017-1000083, USN-3351-1

## What is CVE-2017-1000083?

CVE-2017-1000083 is a high-severity command injection vulnerability in Debian Debian Linux, published on 5 Sep 2017. 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

backend/comics/comics-document.c (aka the comic book backend) in GNOME Evince before 3.24.1 allows remote attackers to execute arbitrary commands via a .cbt file that is a TAR archive containing a filename beginning with a "--" command-line option substring, as demonstrated by a --checkpoint-action=exec=bash at the beginning of the filename.

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

It affects 8 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `evince` | Red Hat:enterprise_linux:7::client | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-browser-plugin` | Red Hat:enterprise_linux:7::client | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-dvi` | Red Hat:enterprise_linux:7::client | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-libs` | Red Hat:enterprise_linux:7::client | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-nautilus` | Red Hat:enterprise_linux:7::client | All versions | 0:3.22.1-5.2.el7_4 |
| `evince` | Red Hat:enterprise_linux:7::server | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-browser-plugin` | Red Hat:enterprise_linux:7::server | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-dvi` | Red Hat:enterprise_linux:7::server | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-libs` | Red Hat:enterprise_linux:7::server | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-nautilus` | Red Hat:enterprise_linux:7::server | All versions | 0:3.22.1-5.2.el7_4 |
| `evince` | Red Hat:enterprise_linux:7::workstation | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-browser-plugin` | Red Hat:enterprise_linux:7::workstation | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-dvi` | Red Hat:enterprise_linux:7::workstation | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-libs` | Red Hat:enterprise_linux:7::workstation | All versions | 0:3.22.1-5.2.el7_4 |
| `evince-nautilus` | Red Hat:enterprise_linux:7::workstation | All versions | 0:3.22.1-5.2.el7_4 |
| `evince` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 3.20.1-6.14.1 |
| `evince` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 3.20.1-6.16.1 |
| `evince` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 3.20.2-6.19.15 |
| `evince` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 3.20.1-6.16.1 |
| `evince` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 3.20.2-6.19.15 |
| `evince` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 3.10.3-2.3.1 |
| `evince` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 3.20.1-6.14.1 |
| `evince` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 3.20.1-6.16.1 |
| `evince` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 3.20.2-6.19.15 |
| `evince` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 3.20.1-6.16.1 |
| `evince` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 3.20.2-6.19.15 |
| `evince` | SUSE:Linux Enterprise Server 12-LTSS | All versions | 3.10.3-2.3.1 |
| `evince` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 3.20.1-6.14.1 |
| `evince` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 3.20.1-6.16.1 |
| `evince` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 3.20.2-6.19.15 |
| `evince` | SUSE:Linux Enterprise Server for SAP Applications 12 | All versions | 3.10.3-2.3.1 |
| `evince` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 3.10.3-2.3.1 |
| `evince` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 3.20.1-6.14.1 |
| `evince` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 3.20.1-6.16.1 |

Products: Debian Debian Linux, Gnome Evince, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation.

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

Upgrade to a fixed version.

## Is CVE-2017-1000083 being exploited?

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

Public exploit code:

- Evince CBT File Command Injection (metasploit)
- https://github.com/matlink/evince-cve-2017-1000083 (github_poc): https://github.com/matlink/evince-cve-2017-1000083
- https://github.com/matlink/cve-2017-1000083-atril-nautilus (github_poc): https://github.com/matlink/cve-2017-1000083-atril-nautilus
- Evince 3.24.0 - Command Injection (exploitdb)
- Evince - CBT File Command Injection (Metasploit) (exploitdb)
- Evince - CBT File Command Injection (Metasploit) (exploitdb)

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-1000083 is a high-severity command injection vulnerability in Debian Debian Linux, published on 5 Sep 2017. 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-2017-1000083 exists.

Affected product: Debian Debian Linux. 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-1000083/ (Markdown: https://insights.sbomify.com/CVE-2017-1000083/index.md)
```

## Sources

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

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