[Bug 1885874] New: double free in sss_to_sudoers
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1885874
Bug ID: 1885874
Summary: double free in sss_to_sudoers
Product: Fedora
Version: 32
OS: Linux
Status: NEW
Component: sssd
Severity: high
Assignee: sssd-maintainers(a)lists.fedoraproject.org
Reporter: avi.kivity(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: abokovoy(a)redhat.com, atikhono(a)redhat.com,
jhrozek(a)redhat.com, lslebodn(a)redhat.com,
mzidek(a)redhat.com, pbrezina(a)redhat.com,
rharwood(a)redhat.com, sbose(a)redhat.com,
ssorce(a)redhat.com,
sssd-maintainers(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Description of problem:
Running 'sudo -s' crashes with
free(): double free detected in tcache 2
Version-Release number of selected component (if applicable):
sudo-1.9.2-1.fc32.x86_64
sssd-2.3.1-2.fc32.x86_64
How reproducible:
Always (on one machine)
Steps to Reproduce:
1. sudo -s
Actual results:
free(): double free detected in tcache 2
Expected results:
Root superpowers
Additional info:
This is a freeipa enrolled machine.
Backtrace:
(gdb) bt
#0 0x00007fdb051ae9e5 in raise () from /lib64/libc.so.6
#1 0x00007fdb05197895 in abort () from /lib64/libc.so.6
#2 0x00007fdb051f2857 in __libc_message () from /lib64/libc.so.6
#3 0x00007fdb051f9d7c in malloc_printerr () from /lib64/libc.so.6
#4 0x00007fdb051fb38d in _int_free () from /lib64/libc.so.6
#5 0x00007fdb056fa205 in sss_sudo_free_values () from
/usr/lib64/libsss_sudo.so
#6 0x00007fdaf779faaf in sss_rule_to_priv (rc_out=<synthetic pointer>,
rule=0x564ee50595d0, handle=0x564ee5055690) at ./sssd.c:336
#7 sss_to_sudoers (sss_result=0x564ee5057d50, handle=0x564ee5055690) at
./sssd.c:398
#8 sudo_sss_query (nss=<optimized out>, pw=<optimized out>) at ./sssd.c:684
#9 0x00007fdaf778f9b9 in sudoers_lookup (snl=<optimized out>,
pw=0x564ee5054d78, validated=validated@entry=96, pwflag=pwflag@entry=0) at
./parse.c:297
#10 0x00007fdaf77994ca in sudoers_policy_main (argc=argc@entry=1,
argv=argv@entry=0x564ee504aa80, pwflag=pwflag@entry=0,
env_add=env_add@entry=0x0, verbose=verbose@entry=false,
closure=closure@entry=0x7fff1050fc70) at ./sudoers.c:368
#11 0x00007fdaf7792090 in sudoers_policy_check (argc=1, argv=0x564ee504aa80,
env_add=0x0, command_infop=0x7fff1050fd30, argv_out=0x7fff1050fd38,
user_env_out=0x7fff1050fd40,
errstr=0x7fff1050fd58) at ./policy.c:974
#12 0x0000564ee349b14d in policy_check (user_env_out=0x7fff1050fd40,
argv_out=0x7fff1050fd38, command_info=0x7fff1050fd30, env_add=0x0,
argv=0x564ee504aa80, argc=1) at ./sudo.c:1162
#13 main (argc=<optimized out>, argv=<optimized out>, envp=0x7fff1050ffd0) at
./sudo.c:267
(gdb)
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
3 years, 2 months
[Bug 1897205] New: SSSD fails to start when run as non-root user
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1897205
Bug ID: 1897205
Summary: SSSD fails to start when run as non-root user
Product: Fedora
Version: 33
OS: Linux
Status: NEW
Component: sssd
Severity: urgent
Assignee: sssd-maintainers(a)lists.fedoraproject.org
Reporter: apeetham(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: abokovoy(a)redhat.com, atikhono(a)redhat.com,
jhrozek(a)redhat.com, lslebodn(a)redhat.com,
mzidek(a)redhat.com, pbrezina(a)redhat.com,
rharwood(a)redhat.com, sbose(a)redhat.com,
ssorce(a)redhat.com,
sssd-maintainers(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Description of problem:
SSSD service fails to restart, when "user = sssd" is set in SSSD.CONF, we don't
see this behaviour in downstream RHEL-8.3 / RHEL-8.4 systems.
Version-Release number of selected component (if applicable):
sssd-2.4.0-2.fc33.x86_64
libsss_simpleifp-2.4.0-2.fc33.x86_64
How reproducible: Always
Steps to Reproduce:
1. Configure sssd.conf as follows:
[sssd]
config_file_version = 2
reconnection_retries = 3
sbus_timeout = 30
services = nss, pam, ifp
debug_level = 0xFFF0
user = sssd
[nss]
filter_groups = root
filter_users = root
reconnection_retries = 3
[pam]
reconnection_retries = 3
[ifp]
allowed_uids = root
user_attributes = +mail, +givenname, +sn
debug_level = 0xFFF0
2. Restart SSSD service, it fails with error.
# systemctl restart sssd; systemctl status sssd
Job for sssd.service failed because the control process exited with error code.
See "systemctl status sssd.service" and "journalctl -xe" for details.
● sssd.service - System Security Services Daemon
Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor
preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2020-11-12
20:27:20 IST; 10ms ago
Process: 6678 ExecStart=/usr/sbin/sssd -i ${DEBUG_LOGGER} (code=exited,
status=4)
Main PID: 6678 (code=exited, status=4)
CPU: 15ms
Nov 12 20:27:20 mojito.redhat.com systemd[1]: Failed to start System Security
Services Daemon.
3. Below is the sssd.log contents, logged right after service restart:
(2020-11-12 20:27:20): [sssd] [monitor_quit_signal] (0x2000): Received shutdown
command
(2020-11-12 20:27:20): [sssd] [monitor_quit_signal] (0x0040): Monitor received
Terminated: terminating children
(2020-11-12 20:27:20): [sssd] [monitor_quit] (0x0040): Returned with: 0
(2020-11-12 20:27:20): [sssd] [monitor_quit] (0x0020): Terminating [ifp][6526]
(2020-11-12 20:27:20): [sssd] [monitor_quit] (0x0020): Child [ifp] exited
gracefully
(2020-11-12 20:27:20): [sssd] [monitor_quit] (0x0020): Terminating [pam][6525]
(2020-11-12 20:27:20): [sssd] [monitor_quit] (0x0020): Child [pam] terminated
with a signal
(2020-11-12 20:27:20): [sssd] [monitor_quit] (0x0020): Terminating [nss][6524]
(2020-11-12 20:27:20): [sssd] [monitor_quit] (0x0020): Child [nss] exited
gracefully
(2020-11-12 20:27:20): [sssd] [monitor_quit] (0x0020): Terminating
[implicit_files][6523]
(2020-11-12 20:27:20): [sssd] [monitor_quit] (0x0020): Child [implicit_files]
exited gracefully
(2020-11-12 20:27:20): [sssd] [watch_ctx_destructor] (0x2000): Closing inotify
fd 0
(2020-11-12 20:27:20:592247): [sssd] [get_service_user] (0x0010): Failed to set
allowed UIDs.
(2020-11-12 20:27:20:592289): [sssd] [get_monitor_config] (0x0020): Failed to
get the unprivileged user
(2020-11-12 20:27:20:592325): [sssd] [main] (0x0020): SSSD couldn't load the
configuration database.
(2020-11-12 20:27:20:860946): [sssd] [get_service_user] (0x0010): Failed to set
allowed UIDs.
(2020-11-12 20:27:20:861023): [sssd] [get_monitor_config] (0x0020): Failed to
get the unprivileged user
(2020-11-12 20:27:20:861077): [sssd] [main] (0x0020): SSSD couldn't load the
configuration database.
(2020-11-12 20:27:21:099530): [sssd] [get_service_user] (0x0010): Failed to set
allowed UIDs.
(2020-11-12 20:27:21:099570): [sssd] [get_monitor_config] (0x0020): Failed to
get the unprivileged user
(2020-11-12 20:27:21:099609): [sssd] [main] (0x0020): SSSD couldn't load the
configuration database.
(2020-11-12 20:27:21:354551): [sssd] [get_service_user] (0x0010): Failed to set
allowed UIDs.
(2020-11-12 20:27:21:354631): [sssd] [get_monitor_config] (0x0020): Failed to
get the unprivileged user
(2020-11-12 20:27:21:354678): [sssd] [main] (0x0020): SSSD couldn't load the
configuration database.
(2020-11-12 20:27:21:596433): [sssd] [get_service_user] (0x0010): Failed to set
allowed UIDs.
(2020-11-12 20:27:21:596565): [sssd] [get_monitor_config] (0x0020): Failed to
get the unprivileged user
(2020-11-12 20:27:21:596672): [sssd] [main] (0x0020): SSSD couldn't load the
configuration database.
Actual results:
SSSD fails to restart.
Expected results:
Like rhel-8.4, sssd service should restart without issues.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
3 years, 2 months