• Nikias Bassen's avatar
    Make sure to copy hash table entries properly when cloning array/dict nodes · e1a5d60e
    Nikias Bassen authored
    As mentioned in #142, plist_copy_node() was not correctly handling the hash
    tables when cloning array or dict nodes; it incorrectly filled the hash table
    with the original child node info, which effectively would lead to a
    segmentation fault / UaF if the original array/dict would be freed followed
    by an attempt to access an element in the new hash table.
    e1a5d60e
Name
Last commit
Last update
..
Array.cpp Loading commit data...
Boolean.cpp Loading commit data...
Data.cpp Loading commit data...
Date.cpp Loading commit data...
Dictionary.cpp Loading commit data...
Integer.cpp Loading commit data...
Key.cpp Loading commit data...
Makefile.am Loading commit data...
Node.cpp Loading commit data...
Real.cpp Loading commit data...
String.cpp Loading commit data...
Structure.cpp Loading commit data...
Uid.cpp Loading commit data...
base64.c Loading commit data...
base64.h Loading commit data...
bplist.c Loading commit data...
bytearray.c Loading commit data...
bytearray.h Loading commit data...
hashtable.c Loading commit data...
hashtable.h Loading commit data...
libplist++.pc.in Loading commit data...
libplist.pc.in Loading commit data...
plist.c Loading commit data...
plist.h Loading commit data...
ptrarray.c Loading commit data...
ptrarray.h Loading commit data...
strbuf.h Loading commit data...
time64.c Loading commit data...
time64.h Loading commit data...
time64_limits.h Loading commit data...
xplist.c Loading commit data...