-
-
Couldn't load subscription status.
- Fork 33.2k
gh-115952: Fix potential virtual memory allocation denial of service in the pickle module #119204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 8 commits
822230d
88f1461
048099b
d9d1d1d
6f6f765
d0e667e
3462d0e
becbd25
b257974
1e487ca
184984d
f0c0728
1f4e2f1
c72d095
e89bfea
a80106c
01bc6b9
20aa1bf
ab58869
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| Fix a vulnerability in the :mod:`pickle` module which allowed to consume | ||
|
||
| arbitrary large amount of memory when loading a small data which does not | ||
| even involve arbitrary code execution. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't use an ill-defined word such as "safe" in the name. Just describe what it does.
chunked_file_read()makes more sense. Same withSAFE_BUF_SIZEjust call it_READ_BUF_SIZE(with an underscore prefix so it isn't considered a public API).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that there is
_safe_readinhttp.client, although ironically it is vulnerable to this kind of issue.I afraid that name like
chunked_file_readcould be misleading, as the data is not read by fixed size chunks. I guess this is what leads you to misunderstanding about the O(N^2) behavior.