# CVE-2014-2888: sfpagent Command Injection vulnerability

> Remote attackers can execute arbitrary commands via shell metacharacters in the module name of a JSON request to the sfpagent Ruby gem.

- **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:** 23 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vm28-mrm7-fpjq

## What is CVE-2014-2888?

CVE-2014-2888 is a high-severity command injection vulnerability in n/a, published on 23 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

lib/sfpagent/bsig.rb in the sfpagent gem before 0.4.15 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in the module name in a JSON request.

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sfpagent` | RubyGems | All versions | 0.4.15 |
| `sfpagent` | RubyGems | All versions | 0.4.15 |

Products: Herry Sfpagent.

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

Upgrade sfpagent to 0.4.15 or later.

## Is CVE-2014-2888 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2888 is a high-severity command injection vulnerability in n/a, published on 23 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-2888 in the wild and no public exploit code.

Affected packages and fixed versions:
- sfpagent (RubyGems): affected all versions; fixed in 0.4.15
- sfpagent (RubyGems): affected all versions; fixed in 0.4.15

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

## Sources

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

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