You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The IMAP4 protocol supports "literal" syntax, when one side specifies the size of the data and then sends the specified amount of bytes. The imaplib client reads such data with a single read(size) call, and therefore is affected by the general vulnerability in the read() method -- it allocates the amount of memory that came from untrusted source. Just an attempt to connect to the malicious IMAP4 server can send your Python program in swap.
Activity
pythongh-119511: Fix OOM vulnerability in imaplib
pythongh-119511: Fix OOM vulnerability in imaplib
gh-119511: Fix a potential denial of service in imaplib (#119514)
pythongh-119511: Fix a potential denial of service in imaplib (python…
pythongh-119511: Fix a potential denial of service in imaplib (python…
pythongh-119511: Fix a potential denial of service in imaplib (python…
pythongh-119511: Fix a potential denial of service in imaplib (python…
[3.13] gh-119511: Fix a potential denial of service in imaplib (GH-11…
[3.12] gh-119511: Fix a potential denial of service in imaplib (GH-11…
[3.11] gh-119511: Fix a potential denial of service in imaplib (GH-11…
[3.10] gh-119511: Fix a potential denial of service in imaplib (GH-11…
[3.9] gh-119511: Fix a potential denial of service in imaplib (GH-119514
[3.9] pythongh-119511: Fix a potential denial of service in imaplib (p…