Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update vulnerable Rubocop once update available (CVE-2017-8418) #756

Closed
david-a-wheeler opened this issue May 29, 2017 · 2 comments
Closed
Labels

Comments

@david-a-wheeler
Copy link
Collaborator

There is a security alert for rubocop; details below. It's a /tmp vulnerability; "Malicious local users could exploit this to tamper with cache files belonging to other users."

Nobody should have untrusted (other) local users on the machines with direct commit rights anyway, so I'm documenting that as a constraint in security.md, and we'll update when an update is available. So this should not affect us.

Here are the details:

 Gems_big Alerts for rubocop
Security alert open on May 29, 2017 08:39
CVE-2017-8418 - Insecure use of /tmp
RuboCop uses /tmp to store cache files insecurely.
Malicious local users could exploit this to tamper with cache files belonging to other users.

    Fixed versions: 0.49.1
    Identifier: CVE-2017-8418
    Solution: There is no solution for this vulnerability at the moment.
    Credit: Jakub Wilk
    Sources: https://github.com/bbatsov/rubocop/issues/4336
    https://github.com/bbatsov/rubocop/commit/dcb258fabd5f2624c1ea0e1634763094590c09d7 
@dankohn
Copy link
Contributor

dankohn commented May 29, 2017

We're also waiting for a new RuboCop to fix this non-security issue: rubocop/rubocop#4412 (comment)

@david-a-wheeler
Copy link
Collaborator Author

Jason - thanks. Now if we could only get the mail gem to work that quickly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants