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

> Remote attackers can execute arbitrary code via shell metacharacters in podcast filenames, requiring user interaction to play the item.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-14500, DLA-1104-1, DSA-3977-1, GHSA-372j-rcwj-w67h, UBUNTU-CVE-2017-14500

## What is CVE-2017-14500?

CVE-2017-14500 is a high-severity command injection vulnerability in n/a, published on 17 Sep 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

Improper Neutralization of Special Elements used in an OS Command in the podcast playback function of Podbeuter in Newsbeuter 0.3 through 2.9 allows remote attackers to perform user-assisted code execution by crafting an RSS item with a media enclosure (i.e., a podcast file) that includes shell metacharacters in its filename, related to pb_controller.cpp and queueloader.cpp, a different vulnerability than CVE-2017-12904.

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

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

It affects 1 product.


Products: Newsbeuter Newsbeuter.

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

Apply the vendor's patch.

## Is CVE-2017-14500 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-3907](https://insights.sbomify.com/CVE-2008-3907/): Command injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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