# CVE-2014-3790: Privilege escalation in n/a

> Authenticated users can escape a chroot jail in Ruby vSphere Console to execute arbitrary commands as root on VMware vCenter Server Appliance.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-728j-xgf7-pwf4

## What is CVE-2014-3790?

CVE-2014-3790 is a critical vulnerability in n/a, published on 1 Jun 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Ruby vSphere Console (RVC) in VMware vCenter Server Appliance allows remote authenticated users to execute arbitrary commands as root by escaping from a chroot jail.

Weakness: CWE-264

## Which versions are affected by CVE-2014-3790?

It affects 1 product.


Products: Vmware Vcenter Server Appliance.

## How do I fix CVE-2014-3790?

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

## Is CVE-2014-3790 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-3079](https://insights.sbomify.com/CVE-2013-3079/): Code injection in n/a (critical 9.0)
- [CVE-2013-3080](https://insights.sbomify.com/CVE-2013-3080/): Missing authorization in n/a (critical 9.0)
- [CVE-2014-3797](https://insights.sbomify.com/CVE-2014-3797/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2014-8371](https://insights.sbomify.com/CVE-2014-8371/): Security feature bypass in n/a (medium 4.3)
- [CVE-2013-3107](https://insights.sbomify.com/CVE-2013-3107/): Auth bypass in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3790 and fix it if it is affected.

What it is: CVE-2014-3790 is a critical vulnerability in n/a, published on 1 Jun 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-3790 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-2014-3790/ (Markdown: https://insights.sbomify.com/CVE-2014-3790/index.md)
```

## Sources

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

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