[New-bugs-announce] [issue13334] Erroneous Size check in
report at bugs.python.org
Thu Nov 3 13:50:02 CET 2011
New submission from david <db.pub.mail at gmail.com>:
The _PyString_Resize function in stringobject.c takes in a PyObject ** and a Py_ssize_t newsize. Where Py_ssize_t is often a typedef for ssize_t(a signed version of size_t). As such the newsize parameter could be negative.
The code checks for when the newsize is negative like so:
_PyString_Resize(PyObject **pv, Py_ssize_t newsize)
if (!PyString_Check(v) || Py_REFCNT(v) != 1 || newsize < 0 ||
*pv = 0;
Unfortunately, a few lines below it does the following:
*pv = (PyObject *)
PyObject_REALLOC((char *)v, PyStringObject_SIZE + newsize);
so now if PyStringObject_SIZE + newsize is enough to wrap around then realloc through python will end up allocating insufficient space for the 'new' string. The python interpreter is likely to crash on this line -->
sv->ob_sval[newsize] = '\0';
I haven't tried to reproduce this in the python interpreter.
IMHO the code should be checking that newline + PyStringObject_SIZE is non-negative.
 - http://svn.python.org/projects/python/trunk/Objects/stringobject.c
title: Erroneous Size check in
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce