[issue24802] PyFloat_FromString Buffer Over-read

Changes by Eric V. Smith : -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue24802] PyFloat_FromString Buffer Over-read

Changes by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue24802] PyFloat_FromString Buffer Over-read

Changes by Serhiy Storchaka : -- type: behavior -> crash ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue24802] PyFloat_FromString Buffer Over-read

Changes by Serhiy Storchaka : -- assignee: -> serhiy.storchaka components: +Interpreter Core nosy: +serhiy.storchaka stage: -> patch review type: security -> behavior versions: +Python 2.7, Python 3.4, Python 3.6 ___ Python tracker

[issue24802] PyFloat_FromString Buffer Over-read

John Leitch added the comment: Attaching repro -- Added file: http://bugs.python.org/file40133/PyFloat_FromString_Buffer_Over-read.py ___ Python tracker ___

[issue24802] PyFloat_FromString Buffer Over-read

New submission from John Leitch: Python suffers from a buffer over-read in PyFloat_FromString() that is caused by the incorrect assumption that buffers returned by PyObject_GetBuffer() are null-terminated. This could potentially result in the disclosure of adjacent memory. PyObject * PyFloat_