Skip to content
Fencer Intel
low 2.1

CVE-2014-1234 json

Paratrooper-newrelic Exposes of Sensitive Information to an Unauthorized Actor

published 12y ago modified 4mo ago also GHSA-959j-5g9v-3fpq , EUVD-2017-0198

cvss
2.1
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits
0
none known

Summary

The paratrooper-newrelic gem 1.0.1 for Ruby allows local users to obtain the X-Api-Key value by listing the curl process.

Is CVE-2014-1234 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.51% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • openwall.com http://openwall.com/lists/oss-security/2014/01/08/2 referenced PoC, tagged "exploit" by a source, unverified
  • vapid.dhs.org http://www.vapid.dhs.org/advisories/paratrooper-newrelic-api.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N

Affected packages

ecosystem package affected fixed in
rubygems paratrooper-newrelic
<=1.0.1
 no fix listed

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.