Bug 1392893 - IPA: Uninitialized variable during subdomain check
Summary: IPA: Uninitialized variable during subdomain check
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: SSSD Maintainers
QA Contact: Steeve Goveas
URL:
Whiteboard:
Depends On: 1382598
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-08 12:27 UTC by Marcel Kolaja
Modified: 2020-05-04 10:58 UTC (History)
15 users (show)

Fixed In Version: sssd-1.14.0-43.el7_3.2
Doc Type: Bug Fix
Doc Text:
Previously, the IPA subdomain provider code contained an unitialized variable. As a consequence, the sssd_be process was at a risk of terminating unexpectedly. The underlying source code has been modified to prevent sssd_be from crashing.
Clone Of: 1382598
Environment:
Last Closed: 2016-12-06 17:11:57 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 4246 0 None None None 2020-05-04 10:58:34 UTC
Red Hat Product Errata RHBA-2016:2870 0 normal SHIPPED_LIVE sssd bug fix update 2016-12-06 22:01:38 UTC

Description Marcel Kolaja 2016-11-08 12:27:19 UTC 
This bug has been copied from bug #1382598 and has been proposed
to be backported to 7.3 z-stream (EUS).
Comment 4 Sudhir Menon 2016-11-09 14:35:42 UTC 
Verified as per https://bugzilla.redhat.com/show_bug.cgi?id=1382598#c2 on RHEL7.3u1

ipa-server-4.4.0-14.el7_3.x86_64
sssd-1.14.0-43.el7_3.2.x86_64

[root@master ~]# valgrind /usr/libexec/sssd/sssd_be --domain ipa.test --uid 0 --gid 0
    ==6374== Memcheck, a memory error detector
    ==6374== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
    ==6374== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
    ==6374== Command: /usr/libexec/sssd/sssd_be --domain ipa.test --uid 0 --gid 0
    ==6374==
    ==6374==
    ==6374== HEAP SUMMARY:
    ==6374==     in use at exit: 37,201 bytes in 68 blocks
    ==6374==   total heap usage: 1,433 allocs, 1,365 frees, 313,770 bytes allocated
    ==6374==
    ==6374== LEAK SUMMARY:
    ==6374==    definitely lost: 245 bytes in 4 blocks
    ==6374==    indirectly lost: 0 bytes in 0 blocks
    ==6374==      possibly lost: 5,126 bytes in 19 blocks
    ==6374==    still reachable: 31,830 bytes in 45 blocks
    ==6374==         suppressed: 0 bytes in 0 blocks
    ==6374== Rerun with --leak-check=full to see details of leaked memory
    ==6374==
    ==6374== For counts of detected and suppressed errors, rerun with: -v
    ==6374== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
    ***************************************
Comment 6 errata-xmlrpc 2016-12-06 17:11:57 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2870.html
Note You need to log in before you can comment on or make changes to this bug.