Skip to content

net-imap (RubyGems)

Advisories
29
Latest version
—
License
—
OpenSSF Scorecard
—

How to fix

Upgrading to 0.6.4.1 or later clears every advisory below that has a fix.

Upgrade commands
bundler
bundle update net-imap # Gemfile: gem "net-imap", ">= 0.6.4.1"

Known vulnerabilities

AdvisorySeverityAffectedFixed in
GHSA-46q3-7gv7-qmgg
Net::IMAP: Command Injection via ID command argument
Medium
EPSS 0.18%
< 0.5.15
0.5.15
GHSA-46q3-7gv7-qmgg
Net::IMAP: Command Injection via ID command argument
Medium
EPSS 0.18%
>= 0.6.0, < 0.6.4.1
0.6.4.1
GHSA-c4fp-cxrr-mj66
Net::IMAP: Denial of Service via incomplete raw argument validation
Low
EPSS 0.38%
>= 0.6.0, < 0.6.4.1
0.6.4.1
GHSA-c4fp-cxrr-mj66
Net::IMAP: Denial of Service via incomplete raw argument validation
Low
EPSS 0.38%
< 0.5.15
0.5.15
GHSA-8p34-64r3-mwg8
Net::IMAP: Command Injection via non-synchronizing literal in "raw" argument
Medium
EPSS 0.83%
< 0.5.15
0.5.15
GHSA-8p34-64r3-mwg8
Net::IMAP: Command Injection via non-synchronizing literal in "raw" argument
Medium
EPSS 0.83%
>= 0.6.0, < 0.6.4.1
0.6.4.1
GHSA-hm49-wcqc-g2xg
net-imap vulnerable to command Injection via "raw" arguments to multiple commands
Critical
EPSS 0.43%
< 0.4.24
0.4.24
GHSA-hm49-wcqc-g2xg
net-imap vulnerable to command Injection via "raw" arguments to multiple commands
Critical
EPSS 0.43%
>= 0.5.0, < 0.5.14
0.5.14
GHSA-hm49-wcqc-g2xg
net-imap vulnerable to command Injection via "raw" arguments to multiple commands
Critical
EPSS 0.43%
>= 0.6.0, < 0.6.4
0.6.4
GHSA-75xq-5h9v-w6px
net-imap vulnerable to command Injection via unvalidated Symbol inputs
Medium
EPSS 0.78%
>= 0.6.0, < 0.6.4
0.6.4
GHSA-75xq-5h9v-w6px
net-imap vulnerable to command Injection via unvalidated Symbol inputs
Medium
EPSS 0.78%
>= 0.5.0, < 0.5.14
0.5.14
GHSA-75xq-5h9v-w6px
net-imap vulnerable to command Injection via unvalidated Symbol inputs
Medium
EPSS 0.78%
< 0.4.24
0.4.24
GHSA-87pf-fpwv-p7m7
net-imap vulnerable to denial of service via high iteration count for `SCRAM-*` authentication
Medium
EPSS 0.30%
>= 0.5.0, < 0.5.14
0.5.14
GHSA-87pf-fpwv-p7m7
net-imap vulnerable to denial of service via high iteration count for `SCRAM-*` authentication
Medium
EPSS 0.30%
>= 0.6.0, < 0.6.4
0.6.4
GHSA-87pf-fpwv-p7m7
net-imap vulnerable to denial of service via high iteration count for `SCRAM-*` authentication
Medium
EPSS 0.30%
>= 0.4.0, < 0.4.24
0.4.24
GHSA-q2mw-fvj9-vvcw
net-imap has quadratic complexity when reading response literals
High
EPSS 0.41%
>= 0.5.0, < 0.5.14
0.5.14
GHSA-q2mw-fvj9-vvcw
net-imap has quadratic complexity when reading response literals
High
EPSS 0.41%
>= 0.6.0, < 0.6.4
0.6.4
GHSA-q2mw-fvj9-vvcw
net-imap has quadratic complexity when reading response literals
High
EPSS 0.41%
< 0.4.24
0.4.24
GHSA-vcgp-9326-pqcp
net-imap vulnerable to STARTTLS stripping via invalid response timing
High
EPSS 0.31%
>= 0.4.0, < 0.4.24
0.4.24
GHSA-vcgp-9326-pqcp
net-imap vulnerable to STARTTLS stripping via invalid response timing
High
EPSS 0.31%
< 0.3.10
0.3.10
GHSA-vcgp-9326-pqcp
net-imap vulnerable to STARTTLS stripping via invalid response timing
High
EPSS 0.31%
>= 0.5.0, < 0.5.14
0.5.14
GHSA-vcgp-9326-pqcp
net-imap vulnerable to STARTTLS stripping via invalid response timing
High
EPSS 0.31%
>= 0.6.0, < 0.6.4
0.6.4
GHSA-j3g3-5qv5-52mj
net-imap rubygem vulnerable to possible DoS by memory exhaustion
Medium
EPSS 0.49%
< 0.2.5
0.2.5
GHSA-j3g3-5qv5-52mj
net-imap rubygem vulnerable to possible DoS by memory exhaustion
Medium
EPSS 0.49%
>= 0.3.0, < 0.3.9
0.3.9
GHSA-j3g3-5qv5-52mj
net-imap rubygem vulnerable to possible DoS by memory exhaustion
Medium
EPSS 0.49%
>= 0.4.0, < 0.4.20
0.4.20
GHSA-j3g3-5qv5-52mj
net-imap rubygem vulnerable to possible DoS by memory exhaustion
Medium
EPSS 0.49%
>= 0.5.0, < 0.5.7
0.5.7
GHSA-7fc5-f82f-cx69
Possible DoS by memory exhaustion in net-imap
Medium
EPSS 0.63%
>= 0.3.2, < 0.3.8
0.3.8
GHSA-7fc5-f82f-cx69
Possible DoS by memory exhaustion in net-imap
Medium
EPSS 0.63%
>= 0.4.0, < 0.4.19
0.4.19
GHSA-7fc5-f82f-cx69
Possible DoS by memory exhaustion in net-imap
Medium
EPSS 0.63%
>= 0.5.0, < 0.5.6
0.5.6
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor