Bump net-imap from 0.3.4 to 0.3.9

Open dependabot[bot] opened this issue 9 months ago • 0 comments

Bumps net-imap from 0.3.4 to 0.3.9.

Release notes

v0.3.9

What's Changed

This release backports two features to prevent unbounded memory use: the response_handlers keyword argument to Net::IMAP.new so response handlers can be added before the server can send any responses (ruby/net-imap#438), and the max_response_size config attribute (ruby/net-imap#446).

[!NOTE] The default max_response_size is nil (unlimited), to avoid backward compatibility issues with secure connections to trusted servers that are well-behaved. It can be configured more conservatively to guard against untrusted servers (for example, connecting to user-provided hostnames). It is the responsibility of net-imap users to configure their client appropriately for the server they are connecting to.

Added

✨ Backport response_handlersoption to new by @nevans in ruby/net-imap#438

Backports #419, and #427

✨ Limit max_response_size by @nevans in ruby/net-imap#446

Backports #444

Fixed

🐛 Use Range#size vs Range#count for uid-set limit by @nevans in ruby/net-imap#411

Documentation

📚 Docs: receiver thread, server responses, connection state by @nevans in ruby/net-imap#437

Backports #418, and only the documentation from #416.

Other Changes

♻️ Backport ResponseReader by @nevans in ruby/net-imap#439

Backports #422, #433, #434, and #435

Full Changelog: https://github.com/ruby/net-imap/compare/v0.3.8...v0.3.9

v0.3.8

What's Changed

🔒 Security Fix

Mitigates CVE-2025-25186 (GHSA-7fc5-f82f-cx69): A malicious server can exhaust client memory by sending APPENDUID or COPYUID responses with very large uid-set ranges. Net::IMAP::UIDPlusData expands these ranges into arrays of integers.

Fix with minor API changes

For v0.3.8, this option is not available. Upgrade to v0.4.19, v0.5.6, or higher to replace UIDPlusData with AppendUIDData and CopyUIDData. These classes store their UIDs as Net::IMAP::SequenceSet objects (not expanded into arrays of integers).

Mitigate with backward compatible API

This release mitigates the attack by crashing if a server tries to send a uid-set that represents more than 10,000 numbers. This should be larger than almost all legitimate COPYUID or APPENDUID responses and would limit the array to only 80KB (on a 64 bit system).

For v0.3.8, this option is not configurable. Upgrade to v0.4.19, v0.5.6, or higher to configure this limit.

Please Note: unhandled responses

If the client does not add response handlers to prune unhandled responses, a malicious server can still eventually exhaust all client memory, by repeatedly sending malicious responses. However, net-imap has always retained unhandled responses, and it has always been necessary for long-lived connections to prune these responses. This is not significantly different from connecting to a trusted server with a long-lived connection. To limit the maximum number of retained responses, a simple handler might look something like the following:
limit = 1000
imap.add_response_handler do |resp|
  name = resp.name
  code = resp.data.code&.name if resp.data.in?(Net::IMAP::ResponseText)
  # before 0.4.0:
</tr></table> 

... (truncated)

Commits

d86186d 🔖 Bump version to v0.3.9
2aadab9 🔀 Merge pull request #446 from ruby/backport/v0.3-max_response_size
e005925 ✅ Fix backport to not-imap 0.3 and ruby 2.6
ae0fa01 ✅ Fix backport compatibility with ruby 2.7
158cfdf ✨ Make max_response_size configurable [🚧 partial]
53ceba1 ✨ Limit max response size to 512MiB (hard-coded)
4d1206e 🔀 Merge pull request #439 from ruby/backport/v0.3-response_reader
19495b8 🔀 Merge pull request #438 from ruby/backport/v0.3-response_handlers
945df80 🔀 Merge pull request #437 from ruby/backport/v0.3-document-response-limits
b0a6039 ✅ Fix backport compatibility with ruby 2.7
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.

Apr 29 '25 01:04 dependabot[bot]