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

> RVM automatically executes code from files in the current directory, allowing attackers to run arbitrary commands when a user navigates to a malicious directory.

- **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:** No
- **Published:** 13 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3xjp-838f-rph3

## What is CVE-2017-1000037?

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

### Official description

RVM automatically loads environment variables from files in $PWD resulting in command execution RVM vulnerable to command injection when automatically loading environment variables from files in $PWD RVM automatically executes hooks located in $PWD resulting in code execution RVM automatically installs gems as specified by files in $PWD resulting in code execution RVM automatically does "bundle install" on a Gemfile specified by .versions.conf in $PWD resulting in code execution

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

It affects 1 product.


Products: Rvm Project Rvm.

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

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

## Is CVE-2017-1000037 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000037 and fix it if it is affected.

What it is: CVE-2017-1000037 is a critical command injection vulnerability in n/a, published on 13 Jul 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-2017-1000037 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-1000037/ (Markdown: https://insights.sbomify.com/CVE-2017-1000037/index.md)
```

## Sources

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

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