# CVE-2013-1945: Other in ruby193

> Insecure LD_LIBRARY_PATH setting in Ruby allows attackers to load malicious libraries, potentially leading to code execution.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** No
- **Published:** 31 Oct 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f29j-vf7h-f9g9

## What is CVE-2013-1945?

CVE-2013-1945 is a low-severity vulnerability in ruby193, published on 31 Oct 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ruby193 uses an insecure LD_LIBRARY_PATH setting.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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

It affects 1 product.


Products: Ruby-Lang Ruby193.

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

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

## Is CVE-2013-1945 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-1945 is a low-severity vulnerability in ruby193, published on 31 Oct 2019. 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-2013-1945 in the wild and no public exploit code.

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

## Sources

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

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