# CVE-2014-1233: Local API Login Credentials Disclosure in paratrooper-pingdom

> Local attackers can expose Pingdom API credentials by inspecting curl process arguments in the paratrooper-pingdom Ruby gem.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fqrr-rrwg-69pv

## What is CVE-2014-1233?

CVE-2014-1233 is a low-severity vulnerability in n/a, published on 10 Jan 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The paratrooper-pingdom gem 1.0.0 for Ruby allows local users to obtain the App-Key, username, and password values by listing the curl process.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

2 open source packages ship an affected version, including paratrooper-pingdom. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `paratrooper-pingdom` | RubyGems | All versions to 1.0.0 | None |
| `paratrooper-pingdom` | RubyGems | All versions to 1.0.0 | None |

Products: Tobias Maier Paratrooper-Pingdom.

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

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

## Is CVE-2014-1233 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-1233 is a low-severity vulnerability in n/a, published on 10 Jan 2014. 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-1233 in the wild and no public exploit code.

Affected packages and fixed versions:
- paratrooper-pingdom (RubyGems): affected all versions up to 1.0.0; no fix listed
- paratrooper-pingdom (RubyGems): affected all versions up to 1.0.0; 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-1233/ (Markdown: https://insights.sbomify.com/CVE-2014-1233/index.md)
```

## Sources

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

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