#5457 ipasam: error while accessing a user which does not have a user-private-group
Closed: Fixed Opened 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:

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

ipa-4-1:

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

master:

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

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

Metadata