CVE-2017-8418 json
RuboCop gem Insecure use of /tmp
published 2017-05-02 9 y ago modified 2026-06-17 4 mo ago also GHSA-wmjf-jpjj-9f3j , EUVD-2017-0354
- cvss
- 3.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
RuboCop 0.48.1 and earlier does not use /tmp in safe way, allowing local users to exploit this to tamper with cache files belonging to other users.
Patch / fix
- rubygems rubocop 0.49.0
- rubocop Debian 14, Debian 13, Debian 12 0.49.1+dfsg-1
debian advisories DEBIAN-CVE-2017-8418
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- openwall.com http://www.openwall.com/lists/oss-security/2017/05/01/14 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/bbatsov/rubocop/issues/4336 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 3.3 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:P/A:N |
| GitHub | 3.0 | 3.3 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | rubocop | <0.49.0 |
0.49.0 |
Classification
- Weakness
-
- CWE-668 Exposure of Resource to Wrong Sphere
References
-
github.com
/rubocop/rubocop/commit/dcb258fabd5f2624c1ea0e1634763094590c09d7
web
-
openwall.com
/lists/oss-security/2017/05/01/14
web, exploit, mailing-list, third-party-advisory
-
github.com
/bbatsov/rubocop/issues/4336
web, exploit, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2017-8418
advisory
-
github.com
/bbatsov/rubocop
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/rubocop/CVE-2017-8418.yml
web
Sources
- CVE List CVE-2017-8418
- GitHub Advisory GHSA-wmjf-jpjj-9f3j
- NVD CVE-2017-8418
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.