🚨 [security] Update mail 2.8.1 → 2.9.1 (minor) - #142
Open
depfu[bot] wants to merge 1 commit into
Open
depfu[bot] wants to merge 1 commit into
depfu[bot] wants to merge 1 commit into
Conversation
depfu
Bot
added
dependencies
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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!
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
Security Advisories 🚨
🚨 Mail: Email address spoofing via malformed RFC 2047 encoded-words
Release Notes
2.9.1
2.9.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
3.5.1
3.4.1
3.4.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Security Advisories 🚨
🚨 Net::IMAP: Denial of Service via incomplete raw argument validation
🚨 Net::IMAP: Command Injection via ID command argument
🚨 Net::IMAP: Command Injection via non-synchronizing literal in "raw" argument
🚨 Net::IMAP: Command Injection via ID command argument
🚨 Net::IMAP: Command Injection via non-synchronizing literal in "raw" argument
🚨 Net::IMAP: Denial of Service via incomplete raw argument validation
🚨 net-imap vulnerable to STARTTLS stripping via invalid response timing
🚨 net-imap has quadratic complexity when reading response literals
🚨 net-imap vulnerable to denial of service via high iteration count for `SCRAM-*` authentication
🚨 net-imap vulnerable to command Injection via "raw" arguments to multiple commands
🚨 net-imap vulnerable to STARTTLS stripping via invalid response timing
🚨 net-imap has quadratic complexity when reading response literals
🚨 net-imap vulnerable to denial of service via high iteration count for `SCRAM-*` authentication
🚨 net-imap vulnerable to command Injection via unvalidated Symbol inputs
🚨 net-imap vulnerable to command Injection via "raw" arguments to multiple commands
🚨 net-imap vulnerable to command Injection via unvalidated Symbol inputs
🚨 net-imap vulnerable to STARTTLS stripping via invalid response timing
🚨 net-imap has quadratic complexity when reading response literals
🚨 net-imap vulnerable to denial of service via high iteration count for `SCRAM-*` authentication
🚨 net-imap vulnerable to command Injection via unvalidated Symbol inputs
🚨 net-imap vulnerable to command Injection via "raw" arguments to multiple commands
🚨 net-imap rubygem vulnerable to possible DoS by memory exhaustion
🚨 net-imap rubygem vulnerable to possible DoS by memory exhaustion
🚨 Possible DoS by memory exhaustion in net-imap
🚨 Possible DoS by memory exhaustion in net-imap
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
0.3.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
0.5.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
0.6.1
0.6.0
0.5.0
0.4.4
0.4.3
0.4.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
🆕 logger (added, 1.7.0)
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.All Depfu comment commands