# CVE-2014-0036: rbovirt uses the rest-client gem with SSL verification disabled

> The rbovirt gem disables SSL verification, allowing remote attackers to perform man-in-the-middle attacks and intercept sensitive data.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-ww79-8xwv-932x

## What is CVE-2014-0036?

CVE-2014-0036 is a medium-severity vulnerability in n/a, published on 17 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The rbovirt gem before 0.0.24 for Ruby uses the rest-client gem with SSL verification disabled, which allows remote attackers to conduct man-in-the-middle attacks via unspecified vectors.

Weakness: CWE-310

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

2 open source packages ship an affected version, including rbovirt. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rbovirt` | RubyGems | All versions | 0.0.24 |
| `rbovirt` | RubyGems | All versions | 0.0.24 |

Products: Amos Benari Rbovirt.

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

Upgrade rbovirt to 0.0.24 or later.

## Is CVE-2014-0036 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-0036 is a medium-severity vulnerability in n/a, published on 17 Apr 2014. 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-2014-0036 in the wild and no public exploit code.

Affected packages and fixed versions:
- rbovirt (RubyGems): affected all versions; fixed in 0.0.24
- rbovirt (RubyGems): affected all versions; fixed in 0.0.24

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-0036/ (Markdown: https://insights.sbomify.com/CVE-2014-0036/index.md)
```

## Sources

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

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