# CVE-2015-9059: Command injection in n/a

> Attackers can execute arbitrary commands via the file transfer feature in picocom due to unsafe shell execution.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-9059, DLA-2259-1, DLA-974-1, GHSA-q4vh-m55v-h7j5, UBUNTU-CVE-2015-9059

## What is CVE-2015-9059?

CVE-2015-9059 is a critical command injection vulnerability in n/a, published on 28 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

picocom before 2.0 has a command injection vulnerability in the 'send and receive file' command because the command line is executed by /bin/sh unsafely.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2015-9059?

It affects 1 product.


Products: Picocom Project Picocom.

## How do I fix CVE-2015-9059?

Upgrade to a fixed version.

## Is CVE-2015-9059 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-9059 and fix it if it is affected.

What it is: CVE-2015-9059 is a critical command injection vulnerability in n/a, published on 28 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-9059 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-2015-9059/ (Markdown: https://insights.sbomify.com/CVE-2015-9059/index.md)
```

## Sources

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

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