#516 Potential memory leak in _nss_sss_*_r()
Closed: Fixed None Opened 13 years ago by sgallagh.

From Coverity:

Calling allocation function "sss_nss_make_request" on "repbuf". [show details]
  309    nret = sss_nss_make_request(SSS_NSS_GETGRGID, &rd,
  310                                &repbuf, &replen, errnop);
...
  326    if (((uint32_t *)repbuf)[0] != 1) {
  327        *errnop = EBADMSG;
Variable "repbuf" going out of scope leaks the storage it points to.
  328        return NSS_STATUS_TRYAGAIN;
  329    }

Present in _nss_sss_getgrgid_r(), _nss_sss_getgrnam_r() and _nss_sss_initgroups_dyn()


Also present in _nss_sss_getpwnam_r() and _nss_sss_getpwuid_r()

Fields changed

owner: somebody => jhrozek

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.2.1

Fields changed

keywords: => coverity

Fields changed

status: new => assigned

Fixed by 51420d0

fixedin: => 1.2.1
resolution: => fixed
status: assigned => closed

Fields changed

rhbz: => 0

Metadata Update from @sgallagh:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.2.1

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1558

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata