summaryrefslogtreecommitdiffstats
path: root/po
diff options
context:
space:
mode:
authorLukas Slebodnik <lslebodn@redhat.com>2014-03-25 17:57:32 +0100
committerJakub Hrozek <jhrozek@redhat.com>2014-04-01 23:26:13 +0200
commit74d6909e7a332df8725e3ec85e6aae79f7abee5d (patch)
treea0bac5975b30955e12559486e8f48816eafdad78 /po
parent577a0e2a90a940fc009e966c7fbe7f9fe39d00f3 (diff)
downloadsssd-74d6909e7a332df8725e3ec85e6aae79f7abee5d.tar.gz
sssd-74d6909e7a332df8725e3ec85e6aae79f7abee5d.tar.xz
sssd-74d6909e7a332df8725e3ec85e6aae79f7abee5d.zip
IPA: Use function sysdb_attrs_get_el in safe way
Function sysdb_attrs_get_el can enlarge array of ldb_message_element in "struct sysdb_attrs" if attribute is not among available attributes. Array will be enlarged with function talloc_realloc but realloc can move array to another place in memory therefore ldb_message_element should not be used after next call of function sysdb_attrs_get_el sysdb_attrs_get_el(netgroup, SYSDB_ORIG_MEMBER_USER, &user_found); sysdb_attrs_get_el(netgroup, SYSDB_ORIG_MEMBER_HOST, &host_found); With netgroups, it is common to omit user or host from netgroup triple. There is very high probability that realloc will be called. it is possible pointer user_found can refer to the old area after the second call of function sysdb_attrs_get_el. Resolves: https://fedorahosted.org/sssd/ticket/2284 Reviewed-by: Sumit Bose <sbose@redhat.com> (cherry picked from commit c048657aa2fbb246b5dc199ef6101bfd6e5eeaea)
Diffstat (limited to 'po')
0 files changed, 0 insertions, 0 deletions