Python 2.7.14 is vulnerable to a Heap-Buffer-Overflow as well as a Heap-Use-After-Free. Python versions prior to 2.7.14 may also be vulnerable and it appears that Python 2.7.17 and prior may also be vulnerable however this has not been confirmed. The vulnerability lies when multiply threads are handling large amounts of data. In both cases there is essentially a race condition that occurs. For the Heap-Buffer-Overflow, Thread 2 is creating the size for a buffer, but Thread1 is already writing to the buffer without knowing how much to write. So when a large amount of data is being processed, it is very easy to cause memory corruption using a Heap-Buffer-Overflow. As for the Use-After-Free, Thread3->Malloc->Thread1->Free's->Thread2-Re-uses-Free'd Memory. The PSRT has stated that this is not a security vulnerability due to the fact that the attacker must be able to run code, however in some situations, such as function as a service, this vulnerability can potentially be used by an attacker to violate a trust boundary, as such the DWF feels this issue deserves a CVE.
Are we affected by this vulnerability?
-Gentoo Security Padawan-
@Maintainers we seem to be affected by this CVE, please confirm if that's the case.
This seems to still be vulnerable, reference SUSE ticket cherry pick patch comments:
> This issue is fixed by upstream patch 6401e5671781eb217ee1afb4603cc0d1b0367ae6. > Since that solution had unintended side-effects, another commit was added on top of it in dbf52e02f18dac6f5f0a64f78932f3dc6efc056b.
@ maintainer(s): can we start stabilization of =dev-lang/python-2.7.15?
Sure. Arch teams, please proceed.
Stable on alpha.
Gentoo Security Padawan
This issue was resolved and addressed in
GLSA 201811-02 at https://security.gentoo.org/glsa/201811-02
by GLSA coordinator Thomas Deutschmann (whissi).
Re-opening for cleanup.
@ Maintainer(s): Please cleanup and drop <dev-lang/python-2.7.15!
cleanup on aisle #6...
Tree is clean: