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

> Attackers can execute arbitrary OS commands by sending malicious PGP signed emails to users with specific PGP verification preferences enabled.

- **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:** Yes
- **Published:** 4 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-7414, GHSA-66jj-9jf3-x628, UBUNTU-CVE-2017-7414

## What is CVE-2017-7414?

CVE-2017-7414 is a high-severity command injection vulnerability in n/a, published on 4 Apr 2017. 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

In Horde_Crypt before 2.7.6, as used in Horde Groupware Webmail Edition 5.x through 5.2.17, OS Command Injection can occur if the user has PGP features enabled in the user's preferences, and has enabled the "Should PGP signed messages be automatically verified when viewed?" preference. To exploit this vulnerability, an attacker can send a PGP signed email (that is maliciously crafted) to the Horde user, who then must either view or preview it.

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

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

It affects 1 product.


Products: Horde Groupware.

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

Upgrade to a fixed version.

## Is CVE-2017-7414 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-7218](https://insights.sbomify.com/CVE-2008-7218/): Other in n/a (critical 10.0)
- [CVE-2008-7219](https://insights.sbomify.com/CVE-2008-7219/): Missing authorization in n/a (critical 10.0)
- [CVE-2019-12095](https://insights.sbomify.com/CVE-2019-12095/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2017-7413](https://insights.sbomify.com/CVE-2017-7413/): Command injection in n/a (high 8.8)
- [CVE-2017-15235](https://insights.sbomify.com/CVE-2017-15235/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-7414 is a high-severity command injection vulnerability in n/a, published on 4 Apr 2017. 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-2017-7414 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-7414/ (Markdown: https://insights.sbomify.com/CVE-2017-7414/index.md)
```

## Sources

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

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