CVE-2014-5000 json
lawn-login exposes database password to unauthorized users
published 2018-01-10 8 y ago modified 2026-06-17 4 mo ago also GHSA-rhgq-vv9x-j4p5 , EUVD-2018-0164
- cvss
- 7.8
- version 3.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 login function in lib/lawn.rb in the lawn-login gem 0.0.7 for Ruby places credentials on the curl command line, which allows local users to obtain sensitive information by listing the process.
Exploit prediction
0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- vapid.dhs.org http://www.vapid.dhs.org/advisories/lawn-login-0.0.7.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | lawn-login | 1 listed version |
no fix listed |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
vapid.dhs.org
/advisories/lawn-login-0.0.7.html
exploit, third-party-advisory
-
openwall.com
/lists/oss-security/2014/07/17/5
mailing-list, third-party-advisory
-
openwall.com
/lists/oss-security/2014/07/07/20
mailing-list, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2014-5000
advisory
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/lawn-login/CVE-2014-5000.yml
web
-
github.com
/skalnik/lawn-login
package
-
web.archive.org
/web/20200229060607/http://www.vapid.dhs.org/advisories/lawn-login-0.0.7.html
web
Sources
- CVE List CVE-2014-5000
- GitHub Advisory GHSA-rhgq-vv9x-j4p5
- NVD CVE-2014-5000
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.