# CVE-2005-2337: Security feature bypass in n/a > Attackers can bypass Ruby's safe level and taint protections to execute disallowed code when processing input via stdin. - **Severity:** High 7.5 (`AV:N/AC:L/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:** 7 Oct 2005 - **Updated:** 7 Aug 2024 - **Also known as:** DSA-860-1, DSA-862-1, DSA-864-1, GHSA-w8mr-4m5w-x8wv, RHSA-2005:799 ## What is CVE-2005-2337? CVE-2005-2337 is a high-severity vulnerability in n/a, published on 7 Oct 2005. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Ruby 1.6.x up to 1.6.8, 1.8.x up to 1.8.2, and 1.9.0 development up to 2005-09-01 allows attackers to bypass safe level and taint flag protections and execute disallowed code when Ruby processes a program through standard input (stdin). ## Which versions are affected by CVE-2005-2337? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `irb` | Red Hat:enterprise_linux:3::as | All versions | 0:1.6.8-9.EL3.4 | | `ruby` | Red Hat:enterprise_linux:3::as | All versions | 0:1.6.8-9.EL3.4 | | `ruby-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:1.6.8-9.EL3.4 | | `ruby-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:1.6.8-9.EL3.4 | | `ruby-docs` | Red Hat:enterprise_linux:3::as | All versions | 0:1.6.8-9.EL3.4 | | `ruby-libs` | Red Hat:enterprise_linux:3::as | All versions | 0:1.6.8-9.EL3.4 | | `ruby-mode` | Red Hat:enterprise_linux:3::as | All versions | 0:1.6.8-9.EL3.4 | | `ruby-tcltk` | Red Hat:enterprise_linux:3::as | All versions | 0:1.6.8-9.EL3.4 | | `irb` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.6.8-9.EL3.4 | | `ruby` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.6.8-9.EL3.4 | | `ruby-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.6.8-9.EL3.4 | | `ruby-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.6.8-9.EL3.4 | | `ruby-docs` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.6.8-9.EL3.4 | | `ruby-libs` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.6.8-9.EL3.4 | | `ruby-mode` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.6.8-9.EL3.4 | | `ruby-tcltk` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.6.8-9.EL3.4 | | `irb` | Red Hat:enterprise_linux:3::es | All versions | 0:1.6.8-9.EL3.4 | | `ruby` | Red Hat:enterprise_linux:3::es | All versions | 0:1.6.8-9.EL3.4 | | `ruby-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:1.6.8-9.EL3.4 | | `ruby-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:1.6.8-9.EL3.4 | | `ruby-docs` | Red Hat:enterprise_linux:3::es | All versions | 0:1.6.8-9.EL3.4 | | `ruby-libs` | Red Hat:enterprise_linux:3::es | All versions | 0:1.6.8-9.EL3.4 | | `ruby-mode` | Red Hat:enterprise_linux:3::es | All versions | 0:1.6.8-9.EL3.4 | | `ruby-tcltk` | Red Hat:enterprise_linux:3::es | All versions | 0:1.6.8-9.EL3.4 | | `irb` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.6.8-9.EL3.4 | | `ruby` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.6.8-9.EL3.4 | | `ruby-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.6.8-9.EL3.4 | | `ruby-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.6.8-9.EL3.4 | | `ruby-docs` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.6.8-9.EL3.4 | | `ruby-libs` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.6.8-9.EL3.4 | | `ruby-mode` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.6.8-9.EL3.4 | | `ruby-tcltk` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.6.8-9.EL3.4 | | `irb` | Red Hat:enterprise_linux:4::as | All versions | 0:1.8.1-7.EL4.2 | | `ruby` | Red Hat:enterprise_linux:4::as | All versions | 0:1.8.1-7.EL4.2 | | `ruby-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:1.8.1-7.EL4.2 | | `ruby-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:1.8.1-7.EL4.2 | | `ruby-docs` | Red Hat:enterprise_linux:4::as | All versions | 0:1.8.1-7.EL4.2 | | `ruby-libs` | Red Hat:enterprise_linux:4::as | All versions | 0:1.8.1-7.EL4.2 | | `ruby-mode` | Red Hat:enterprise_linux:4::as | All versions | 0:1.8.1-7.EL4.2 | | `ruby-tcltk` | Red Hat:enterprise_linux:4::as | All versions | 0:1.8.1-7.EL4.2 | Products: Yukihiro Matsumoto Ruby. ## How do I fix CVE-2005-2337? Upgrade to a fixed version. ## Is CVE-2005-2337 being exploited? There is no known exploitation of CVE-2005-2337 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2005-1992](https://insights.sbomify.com/CVE-2005-1992/): Command injection in n/a (high 7.5) - [CVE-2006-3694](https://insights.sbomify.com/CVE-2006-3694/): Security feature bypass in n/a (medium 6.4) - [CVE-2006-6303](https://insights.sbomify.com/CVE-2006-6303/): Denial of service in n/a (medium 5.0) - [CVE-2006-5467](https://insights.sbomify.com/CVE-2006-5467/): Denial of service in n/a (medium 5.0) - [CVE-2006-1931](https://insights.sbomify.com/CVE-2006-1931/): Denial of service in n/a (medium 5.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2005-2337 and fix it if it is affected. What it is: CVE-2005-2337 is a high-severity vulnerability in n/a, published on 7 Oct 2005. 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-2005-2337 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-2005-2337/ (Markdown: https://insights.sbomify.com/CVE-2005-2337/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2005-2337 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-2337 - OSV: https://osv.dev/vulnerability/CVE-2005-2337 --- From sbomify Insights: https://insights.sbomify.com/CVE-2005-2337/ Summaries are generated and may contain mistakes; the official description above is the record.