#5457 ipasam: error while accessing a user which does not have a user-private-group
Closed: Fixed None Opened 8 years ago by sbose.

There is a memory-access error in the code path to look up a user which does not have a user-private-group, i.e. where POSIX UID and POSIX GID of the primary group are different. To reproduce it

pdbedit -L -v user_name

can be called on an IPA server where ipa-adtrust-install was run.


ipa-4-2:

  • f903fdf ipasam: fix wrong usage of talloc_new()
  • 6974302 ipasam: use more restrictive search filter for group lookup
  • 181d254 ipasam: fix a use-after-free issue

ipa-4-1:

  • c87ce19 ipasam: fix wrong usage of talloc_new()
  • bc0d6b4 ipasam: use more restrictive search filter for group lookup
  • 47df949 ipasam: fix a use-after-free issue

master:

  • 3d6fdab ipasam: fix wrong usage of talloc_new()
  • 99cfc97 ipasam: use more restrictive search filter for group lookup
  • 657cf95 ipasam: fix a use-after-free issue

Metadata Update from @sbose:
- Issue assigned to sbose
- Issue set to the milestone: FreeIPA 4.1.5

7 years ago

Login to comment on this ticket.

Metadata