net-imap
Affected
- introduced
0.6.0, fixed0.6.4(ecosystem)
Fixed versions
0.6.4
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-42246
net-imap vulnerable to STARTTLS stripping via invalid response timing
Summary
A man-in-the-middle attacker can cause Net::IMAP#starttls to return "successfully", without starting TLS.
Details
When using Net::IMAP#starttls to upgrade a plaintext connection to use TLS, a man-in-the-middle attacker can inject a tagged OK response with an easily predictable tag. By sending the response before the client finishes sending the command, the command completes "successfully" before the response handler is registered. This allows #starttls to return without error, but the response handler is never invoked, the TLS connection is never established, and the socket remains unencrypted.
This allows man-in-the-middle attackers to perform a STARTTLS stripping attack, unless the client code explicitly checks Net::IMAP#tls_verified?.
Impact
TLS bypass, leading to cleartext transmission of sensitive information.
Mitigation
#starttls does not establish TLS.STARTTLS with a cleartext port. This is strongly recommended anyway:Net::IMAP#tls_verified? is true, before using the connection after #starttls.High Basis: The source's own band: HIGH
0.6.0, fixed 0.6.4 (ecosystem)0.6.4
The export has no generic command for this ecosystem.
0.5.0, fixed 0.5.14 (ecosystem)0.5.14
The export has no generic command for this ecosystem.
0.4.0, fixed 0.4.24 (ecosystem)0.4.24
The export has no generic command for this ecosystem.
0, fixed 0.3.10 (ecosystem)0.3.10
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0