# CVE-2014-1834: Echor contains Command Injection

> Local attackers can inject arbitrary code via semicolons in credentials within the echor Ruby gem, requiring an upgrade to mitigate.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 2 Feb 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8936-cgj4-phr2

## What is CVE-2014-1834?

CVE-2014-1834 is a high-severity command injection vulnerability in n/a, published on 2 Feb 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The perform_request function in /lib/echor/backplane.rb in echor 0.1.6 Ruby Gem allows local users to inject arbitrary code by adding a semi-colon in their username or password.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `echor` | RubyGems | All versions to 0.1.6 | None |
| `echor` | RubyGems | All versions to 0.1.6 | None |

Products: Echor Project Echor.

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

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

## Is CVE-2014-1834 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-1835](https://insights.sbomify.com/CVE-2014-1835/): Echor Ruby Gem credentials can be stolen via process table monitoring (high 7.8)

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- echor (RubyGems): affected all versions up to 0.1.6; no fix listed
- echor (RubyGems): affected all versions up to 0.1.6; no fix listed

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

## Sources

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

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