![]() 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. ![]() In both cases there is essentially a race condition that occurs. The vulnerability lies when multiply threads are handling large amounts of data. 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. Python 2.7.14 is vulnerable to a Heap-Buffer-Overflow as well as a Heap-Use-After-Free. Support for users manually specifying an abstract namespace socket was added as a bugfix in 3.7.8 and 3.8.3, but users would need to make specific uncommon API calls in order to do that in CPython before 3.9. CPython before 3.9 does not make use of Linux abstract namespace sockets by default. This issue is Linux specific because only Linux supports abstract namespace sockets. The forkserver start method for multiprocessing is not the default start method. ![]() Setting _sockets_supported to False is a workaround. Thus, this allows for local user privilege escalation to the user that any forkserver process is running as. The Python multiprocessing library, when used with the forkserver start method on Linux, allows pickles to be deserialized from any user in the same machine local network namespace, which in many system configurations means any user on the same machine. Python 3.9.x before 3.9.16 and 3.10.x before 3.10.9 on Linux allows local privilege escalation in a non-default configuration.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |