# CVE-2018-16593: Command injection in n/a

> Attackers can execute arbitrary commands on Sony Bravia TVs via the Photo Sharing Plus component due to shell metacharacter injection.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9458-gcgf-4389

## What is CVE-2018-16593?

CVE-2018-16593 is a high-severity command injection vulnerability in n/a, published on 19 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Photo Sharing Plus component on Sony Bravia TV through 8.587 devices allows Shell Metacharacter Injection.

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

## Which versions are affected by CVE-2018-16593?

It affects 8 products.


Products: Sony R5c Firmware, Sony Wd65 Firmware, Sony Wd75 Firmware, Sony We6 Firmware, Sony We75 Firmware, Sony Wf6 Firmware, Sony Xe70 Firmware, Sony Xf70 Firmware.

## How do I fix CVE-2018-16593?

No fix has been published for CVE-2018-16593 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-16593 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-16594](https://insights.sbomify.com/CVE-2018-16594/): Path traversal in n/a (high 8.1)
- [CVE-2018-16595](https://insights.sbomify.com/CVE-2018-16595/): Memory corruption in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-16593 and fix it if it is affected.

What it is: CVE-2018-16593 is a high-severity command injection vulnerability in n/a, published on 19 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-16593 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-2018-16593/ (Markdown: https://insights.sbomify.com/CVE-2018-16593/index.md)
```

## Sources

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

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