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

> Local attackers can escalate privileges and execute arbitrary code via crafted filenames in Bash path autocompletion.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-5932, GHSA-7893-9j9h-935c

## What is CVE-2017-5932?

CVE-2017-5932 is a high-severity command injection vulnerability in n/a, published on 27 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The path autocompletion feature in Bash 4.4 allows local users to gain privileges via a crafted filename starting with a " (double quote) character and a command substitution metacharacter.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Gnu Bash.

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

Apply the vendor's patch.

## Is CVE-2017-5932 being exploited?

There is no known exploitation of CVE-2017-5932 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-2017-5932 and fix it if it is affected.

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

## Sources

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

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