# CVE-2013-2065: Security feature bypass in n/a

> Attackers can bypass Ruby's $SAFE level restrictions in DL and Fiddle libraries, potentially executing unsafe native code.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Nov 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wh77-3w5g-7q6x

## What is CVE-2013-2065?

CVE-2013-2065 is a medium-severity vulnerability in Opensuse Opensuse, published on 2 Nov 2013. 

### Official description

(1) DL and (2) Fiddle in Ruby 1.9 before 1.9.3 patchlevel 426, and 2.0 before 2.0.0 patchlevel 195, do not perform taint checking for native functions, which allows context-dependent attackers to bypass intended $SAFE level restrictions.

Weakness: CWE-264

## Which versions are affected by CVE-2013-2065?

It affects 2 products.


Products: Opensuse Opensuse, Ruby-Lang Ruby.

## How do I fix CVE-2013-2065?

Upgrade to a fixed version.

## Is CVE-2013-2065 being exploited?

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

## Other vulnerabilities in Opensuse Opensuse

- [CVE-2015-5957](https://insights.sbomify.com/CVE-2015-5957/): Memory corruption in n/a (critical 10.0)
- [CVE-2015-0491](https://insights.sbomify.com/CVE-2015-0491/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-2388](https://insights.sbomify.com/CVE-2008-2388/): Integer overflow in n/a (critical 10.0)
- [CVE-2010-1866](https://insights.sbomify.com/CVE-2010-1866/): Integer overflow in n/a (critical 9.8)
- [CVE-2015-0492](https://insights.sbomify.com/CVE-2015-0492/): Other in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2065 and fix it if it is affected.

What it is: CVE-2013-2065 is a medium-severity vulnerability in Opensuse Opensuse, published on 2 Nov 2013. 
Exploitation: There is no known exploitation of CVE-2013-2065 in the wild and no public exploit code.

Affected product: Opensuse Opensuse. 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-2013-2065/ (Markdown: https://insights.sbomify.com/CVE-2013-2065/index.md)
```

## Sources

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

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