# CVE-2013-4203: rgpg Code Injection vulnerability


- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 11 Oct 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-jg4m-q6w8-vrjp

## What is CVE-2013-4203?

CVE-2013-4203 is a high-severity vulnerability in n/a, published on 11 Oct 2013. 

### Official description

The self.run_gpg function in lib/rgpg/gpg_helper.rb in the rgpg gem before 0.2.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in unspecified vectors.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rgpg` | RubyGems | All versions | 0.2.3 |
| `rgpg` | RubyGems | All versions | 0.2.3 |

Products: Richard Cook Rgpg.

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

Upgrade rgpg to 0.2.3 or later.

## Is CVE-2013-4203 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4203 is a high-severity vulnerability in n/a, published on 11 Oct 2013. 
Exploitation: There is no known exploitation of CVE-2013-4203 in the wild and no public exploit code.

Affected packages and fixed versions:
- rgpg (RubyGems): affected all versions; fixed in 0.2.3
- rgpg (RubyGems): affected all versions; fixed in 0.2.3

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

## Sources

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

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