Displaying 1 result from an estimated 1 matches for "ulogd_ret_int32".
2017 Oct 19
0
[Bug 1193] New: Incorrect malloc for SQL statements and missing strings length check
...case, strings can be quite long and might be triggered by users,
making it easy for end-users to crash ulogd.
This patch makes the allocation more "dynamic" for integers and safer for
strings :
- Integers are now reserving only the maximum possible number of bytes they
could use (eg. ULOGD_RET_INT32 lowest value is -2147483648 which is 11
characters long : it will now only allocates 11 bytes for those keys instead of
100)
- For strings, SQL_STRINGSIZE now defines the max length of values (before
being escaped), values longer than SQL_STRINGSIZE will be set to NULL and the
double of SQL_STRI...