CVE-2015-9059

picocom before 2.0 has a command injection vulnerability in the 'send ...

Published 28 May 2017Modified 13 May 2026CWE 77

In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

NVD9.8CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Trivy's own label is CRITICAL. Rated critical by NVD. Rated lower by Ubuntu (medium).

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.

Affected packages and fixed versions

Source	Package	Fixed in
debian 11	picocom	1.7-2
debian 12	picocom	1.7-2
debian 13	picocom	1.7-2
debian 14	picocom	1.7-2
debian 7	picocom	1.7-1+deb7u1
debian 8	picocom	1.7-1+deb8u1
echo	picocom	1.7-2
ubuntu 14.04	picocom	1.7-2build0.14.04.1
ubuntu 16.04	picocom	1.7-2build0.16.04.1
ubuntu 16.04-ESM	picocom	1.7-2build0.16.04.1
ubuntu 16.10	picocom	1.7-2build0.16.10.1
ubuntu 17.04	picocom	1.7-2build0.17.04.1

References

What Attestkeep does with this

Inside your cluster, without you opening a spreadsheet.

KnowsThe scanner refreshes its vulnerability database every six hours.
FindsEvery admitted image is rescanned every 24 hours by default (scan.rescanInterval). When Trivy rates this vulnerability critical for the image's package source, it appears in the image's findings by name. Findings without a fix are left out unless includeUnfixed is on.
Tells youA critical_finding event goes to the channels subscribed to it: e-mail, Slack, Teams, a webhook, Jira, GitLab or GitHub.
RefusesWith a policy that blocks critical findings, a pod with this image is refused at admission, a rollback to it included. Pods already running are not evicted.
RecordsEach decision is recorded with the policy that ran and its hash, then sealed under a signed checkpoint.

Try Attestkeep Read the docs

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.