Skip to content
This repository was archived by the owner on Jul 19, 2022. It is now read-only.

🚨 [security] Update rubyzip: 1.2.1 → 1.2.2 (patch)#13

Open
depfu[bot] wants to merge 1 commit intomasterfrom
depfu/update/rubyzip-1.2.2
Open

🚨 [security] Update rubyzip: 1.2.1 → 1.2.2 (patch)#13
depfu[bot] wants to merge 1 commit intomasterfrom
depfu/update/rubyzip-1.2.2

Conversation

@depfu
Copy link

@depfu depfu bot commented Sep 12, 2018

Welcome to Depfu 👋

This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

Let us know if you have any questions. Thanks so much for giving Depfu a try!

⚠️ No CI detected ⚠️

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

  • Our friends at Travis-CI provide excellent service.
  • Circle CI are good, too, and have a free plan that will cover basic needs.
  • If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
  • If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

It might be necessary to once deactivate and reactivate your project in Depfu for the CI service to be properly detected.


🚨 Your version of rubyzip has known security vulnerabilities 🚨

Advisory: CVE-2018-1000544
Disclosed: June 14, 2018
URL: https://github.com/rubyzip/rubyzip/issues/369

Directory Traversal in rubyzip

rubyzip version 1.2.1 and earlier contains a Directory Traversal vulnerability
in Zip::File component that can result in write arbitrary files to the filesystem.
If a site allows uploading of .zip files, an attacker can upload a malicious file
which contains symlinks or files with absolute pathnames "../" to write arbitrary
files to the filesystem.


🚨 We recommend to merge and deploy this update as soon as possible! 🚨

We've updated a dependency and here is what you need to know:

name version specification old version new version
rubyzip indirect dependency 1.2.1 1.2.2

You should probably take a good look at the info here and the test results before merging this pull request, of course.

What changed?

↗️ rubyzip (indirect, 1.2.1 → 1.2.2) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 54 commits:

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

Depfu Status

@depfu depfu bot added the depfu label Sep 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

Assignees

No one assigned

Labels

depfu

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants