LowGHSA-wmjf-jpjj-9f3jCVE-2017-8418
RuboCop gem Insecure use of /tmp
Published 15 Nov 2017 · Updated 16 Feb 2024
Is your project on an affected rubocop?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
rubocopRubyGems
- Affected
- <0.49.0
- Fixed in
- 0.49.0
Update to the fixed version for your release line, for example:
bundle update --conservative rubocop # Gemfile: '>= 0.49.0'Details
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.
Is GHSA-wmjf-jpjj-9f3j in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected rubocop, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2017-8418
- Linkgithub.com/bbatsov/rubocop/issues/4336
- Linkgithub.com/rubocop/rubocop/commit/dcb258fabd5f2624c1ea0e1634763094590c09d7
- Packagegithub.com/bbatsov/rubocop
- Linkgithub.com/rubysec/ruby-advisory-db/blob/master/gems/rubocop/CVE-2017-8418.yml
- Linkwww.openwall.com/lists/oss-security/2017/05/01/14
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.