[issue41168] Lack of proper checking in PyObject_SetAttr leads to segmentation fault

Petr Viktorin added the comment: Closing; please re-open if you have more info. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

[issue41168] Lack of proper checking in PyObject_SetAttr leads to segmentation fault

Jeffrey Kintscher added the comment: Can you attach the Python source code for the PoC? -- ___ Python tracker ___ ___

[issue41168] Lack of proper checking in PyObject_SetAttr leads to segmentation fault

Change by Jeffrey Kintscher : -- nosy: +Jeffrey.Kintscher ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41168] Lack of proper checking in PyObject_SetAttr leads to segmentation fault

Petr Viktorin added the comment: What kind of security-related issues do you mean? A .pyc file is code; it can do anything. Never run untrusted code, be it .py or .pyc. See also: Lib/test/crashers/bogus_code_obj.py -- nosy: +petr.viktorin ___

[issue41168] Lack of proper checking in PyObject_SetAttr leads to segmentation fault

New submission from Iman Sharafodin : I was testing the latest release of Python 3.6 (June 27, 2020) (https://www.python.org/ftp/python/3.6.11/Python-3.6.11.tgz) and I found that there is lack of enough checks on line number 956 in Objects/object.c file which can cause a segmentation fault.