# CVE-2016-0634: Command injection in n/a

> Remote authenticated users can execute arbitrary code via shell metacharacters in the hostname due to unsafe prompt expansion in Bash.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2017
- **Updated:** 4 Oct 2024
- **Also known as:** ALPINE-CVE-2016-0634, CLEANSTART-2026-GG57088, DEBIAN-CVE-2016-0634, GHSA-h2ww-3j54-pccx, UBUNTU-CVE-2016-0634

## What is CVE-2016-0634?

CVE-2016-0634 is a high-severity command injection vulnerability in n/a, published on 28 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The expansion of '\h' in the prompt string in bash 4.3 allows remote authenticated users to execute arbitrary code via shell metacharacters placed in 'hostname' of a machine.

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

## Which versions are affected by CVE-2016-0634?

It affects 1 product.


Products: Gnu Bash.

## How do I fix CVE-2016-0634?

Apply the vendor's patch.

## Is CVE-2016-0634 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-6278](https://insights.sbomify.com/CVE-2014-6278/): GNU Bash OS Command Injection (high 8.8, exploited in the wild)
- [CVE-2014-7186](https://insights.sbomify.com/CVE-2014-7186/): Memory corruption in n/a (critical 10.0)
- [CVE-2014-7187](https://insights.sbomify.com/CVE-2014-7187/): Memory corruption in n/a (critical 10.0)
- [CVE-2014-6277](https://insights.sbomify.com/CVE-2014-6277/): Code injection in n/a (critical 10.0)
- [CVE-2022-3715](https://insights.sbomify.com/CVE-2022-3715/): Memory corruption in bash (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-0634 and fix it if it is affected.

What it is: CVE-2016-0634 is a high-severity command injection vulnerability in n/a, published on 28 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-0634 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-2016-0634/ (Markdown: https://insights.sbomify.com/CVE-2016-0634/index.md)
```

## Sources

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

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