This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2019-03-26 12:35 by wjq-security, last changed 2022-04-11 14:59 by admin. This issue is now closed.
Pull Requests | |||
---|---|---|---|
URL | Status | Linked | Edit |
PR 12560 | merged | vstinner, 2019-03-26 12:49 | |
PR 12561 | closed | miss-islington, 2019-03-26 13:35 | |
PR 12564 | merged | miss-islington, 2019-03-26 15:21 |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-11 14:59:13 | admin | set | github: 80617 |
2019-03-26 18:35:36 | vstinner | set | status: open -> closed resolution: fixed messages: + msg338912 stage: patch review -> resolved |
2019-03-26 15:39:09 | miss-islington | set | nosy:
+ miss-islington messages: + msg338898 |
2019-03-26 15:21:11 | miss-islington | set | pull_requests: + pull_request12509 |
2019-03-26 13:35:48 | miss-islington | set | pull_requests: + pull_request12506 |
2019-03-26 13:35:45 | vstinner | set | messages: + msg338888 |
2019-03-26 12:51:47 | vstinner | set | versions:
+ Python 3.7, Python 3.8 title: Potential null pointer de-reference vulnerability -> _testcapi.pymem_buffer_overflow() doesn't handle memory allocation failure messages: + msg338880 components: + Tests type: security -> |
2019-03-26 12:49:58 | vstinner | set | keywords:
+ patch stage: patch review pull_requests: + pull_request12505 |
2019-03-26 12:41:57 | xtreak | set | nosy:
+ serhiy.storchaka, xtreak messages: + msg338878 |
2019-03-26 12:38:06 | SilentGhost | set | nosy:
+ vstinner |
2019-03-26 12:35:32 | wjq-security | create |