Description
Bug report
Clang Static Analyzer(CSA), pyrefcon @Snape3058 (http://lcs.ios.ac.cn/~maxt/PyRefcon/ASE-2023.pdf)
- Operating System:
- Linux d18de72e1bb7 5.4.0-196-generic x86
Bug Type: Access released Memory/Use After Free
File: _msg_support.c.em
Commit:
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 179 to 193 in 1fbd99b
Detail: after
Py_DECREF
module_attr
and class_attr
may be released, module_name
and class_name
are possible freed, Causing Access released Memory/Use After Free.
Prove of Content(POC):
static *
poc(PyObject * object) {
PyObject * module_attr = PyObject_GetAttrString(object, "__class__");
char * module_name = NULL;
if (module_attr) {
PyObject *name_attr = PyObject_GetAttrString(module_attr, "__name__");
if (name_attr) {
module_name = (char *)PyUnicode_1BYTE_DATA(name_attr);
Py_DECREF(name_attr);
Py_DECREF(module_attr);
printf("%s", module_name);
}
}
return PyLong_FromLong(0);
}
And this is the correct result.
However, If the garbege collect was triggered between Py_DECREF(object)
and usage of string module_name
, things will become troublesome.
static *
poc(PyObject * object) {
PyObject * module_attr = PyObject_GetAttrString(object, "__class__");
char * module_name = NULL;
if (module_attr) {
PyObject *name_attr = PyObject_GetAttrString(module_attr, "__name__");
if (name_attr) {
module_name = (char *)PyUnicode_1BYTE_DATA(name_attr);
Py_DECREF(name_attr);
Py_DECREF(module_attr);
call_gc_collect();
printf("%s\n", module_name);
}
}
return PyLong_FromLong(0);
}
void call_gc_collect() {
PyObject *gc_module = PyImport_ImportModule("gc");
if (gc_module) {
PyObject *gc_collect = PyObject_GetAttrString(gc_module, "collect");
if (gc_collect && PyCallable_Check(gc_collect)) {
PyObject *result = PyObject_CallObject(gc_collect, NULL);
Py_XDECREF(result);
}
Py_XDECREF(gc_collect);
Py_DECREF(gc_module);
}
}
Finding that module_name has been freed. In this case, I manually call gc.collect() to explain it. In real python environment, GC could free module_name at any time, Causing Use After Free Bug.
How to Fix: I think it's better to use these string before Py_DECREF:
{
PyObject * class_attr = PyObject_GetAttrString(_pymsg, "__class__");
if (class_attr) {
PyObject * name_attr = PyObject_GetAttrString(class_attr, "__name__");
if (name_attr) {
class_name = (char *)PyUnicode_1BYTE_DATA(name_attr);
}
PyObject * module_attr = PyObject_GetAttrString(class_attr, "__module__");
if (module_attr) {
module_name = (char *)PyUnicode_1BYTE_DATA(module_attr);
}
if (!class_name || !module_name) {
return false;
}
snprintf(full_classname_dest, sizeof(full_classname_dest), "%s.%s", module_name, class_name);
Py_XDECREF(module_attr);
Py_XDECREF(name_attr);
Py_DECREF(class_attr);
}
}
Bug Type: Non-Zero Dead Object/Memory Leak
File: _msg_support.c.em
Commit:
Detail: If
_pymessage
has been correctly allocated, function may return NULL without freeing _pymessage
, Causing Non-Zero Dead Object/Memory Leak.
Code:
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 560 to 563 in 1fbd99b
field = PyObject_GetAttrString(_pymessage, "@(member.name)");
if (!field) {
return NULL;
}
Detail: if PyObject_GetAttrString
fail and return NULL
, function will return NULL
causing _pymessage
leak.
Same in any code block fail and return NULL or false:
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 576 to 579 in 1fbd99b
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 584 to 592 in 1fbd99b
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 594 to 598 in 1fbd99b
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 603 to 608 in 1fbd99b
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 620 to 626 in 1fbd99b
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 642 to 645 in 1fbd99b
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 653 to 657 in 1fbd99b
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 664 to 667 in 1fbd99b
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 677 to 680 in 1fbd99b
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 691 to 694 in 1fbd99b
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 700 to 703 in 1fbd99b
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 743 to 747 in 1fbd99b
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 748 to 752 in 1fbd99b
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 754 to 760 in 1fbd99b
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 763 to 769 in 1fbd99b
rosidl_python/rosidl_generator_py/resource/_msg_support.c.em
Lines 795 to 799 in 1fbd99b
Fix: I think it's better to add Py_DECREF(_pymessage)
before return NULL
;