[Solved] Weird Security Issue, some critical commands run without pass

clever · 2020-03-31 09:23:09

Hi
I recently installed archlinux again, after a hdd damage.

kernel: linux-zen
DE: KDE

now the issues is i can run some apps and command without sudo or asking for a password?

e.g. i can disable/enable/start/stop system services (systemctl) without sudo!!!

my sudoer config

# cat /etc/sudoers.d/myusername
myusername ALL=(ALL) ALL

myusername belongs to users group

groups myusername
users

and i wrote no custom polkit.

any idea?!

Last edited by clever (2020-03-31 17:31:57)

schard · 2020-03-31 09:33:22

That's very limited information.
The output of

groups

seems fabricated, since I doubt, that myusername is your actual user name.
Please provide the actual output of

$ id
$ groups

as the respective user.
Also provide the content of

/etc/sudoers

Last edited by schard (2020-03-31 09:33:40)

clever · 2020-03-31 10:01:12

hi schard
ofcourse myusername was notmy actual username, it's knight

here you are

$ id
uid=1000(knight) gid=985(users) groups=985(users)

$ groups
users

#cat /etc/sudoer

## sudoers file.
##
## This file MUST be edited with the 'visudo' command as root.
## Failure to use 'visudo' may result in syntax or file permission errors
## that prevent sudo from running.
##
## See the sudoers man page for the details on how to write a sudoers file.
##

##
## Host alias specification
##
## Groups of machines. These may include host names (optionally with wildcards),
## IP addresses, network numbers or netgroups.
# Host_Alias    WEBSERVERS = www1, www2, www3

##
## User alias specification
##
## Groups of users.  These may consist of user names, uids, Unix groups,
## or netgroups.
# User_Alias    ADMINS = millert, dowdy, mikef

##
## Cmnd alias specification
##
## Groups of commands.  Often used to group related commands together.
# Cmnd_Alias    PROCESSES = /usr/bin/nice, /bin/kill, /usr/bin/renice, \
#                           /usr/bin/pkill, /usr/bin/top
# Cmnd_Alias    REBOOT = /sbin/halt, /sbin/reboot, /sbin/poweroff

##
## Defaults specification
##
## You may wish to keep some of the following environment variables
## when running commands via sudo.
##
## Locale settings
# Defaults env_keep += "LANG LANGUAGE LINGUAS LC_* _XKB_CHARSET"
##
## Run X applications through sudo; HOME is used to find the
## .Xauthority file.  Note that other programs use HOME to find   
## configuration files and this may lead to privilege escalation!
# Defaults env_keep += "HOME"
##
## X11 resource path settings
# Defaults env_keep += "XAPPLRESDIR XFILESEARCHPATH XUSERFILESEARCHPATH"
##
## Desktop path settings
# Defaults env_keep += "QTDIR KDEDIR"
##
## Allow sudo-run commands to inherit the callers' ConsoleKit session
# Defaults env_keep += "XDG_SESSION_COOKIE"
##
## Uncomment to enable special input methods.  Care should be taken as
## this may allow users to subvert the command being run via sudo.
# Defaults env_keep += "XMODIFIERS GTK_IM_MODULE QT_IM_MODULE QT_IM_SWITCHER"
##
## Uncomment to use a hard-coded PATH instead of the user's to find commands
# Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
##
## Uncomment to send mail if the user does not enter the correct password.
# Defaults mail_badpass
##
## Uncomment to enable logging of a command's output, except for
## sudoreplay and reboot.  Use sudoreplay to play back logged sessions.
# Defaults log_output
# Defaults!/usr/bin/sudoreplay !log_output
# Defaults!/usr/local/bin/sudoreplay !log_output
# Defaults!REBOOT !log_output

##
## Runas alias specification
##

##
## User privilege specification
##
root ALL=(ALL) ALL

## Uncomment to allow members of group wheel to execute any command
# %wheel ALL=(ALL) ALL

## Same thing without a password
# %wheel ALL=(ALL) NOPASSWD: ALL

## Uncomment to allow members of group sudo to execute any command
# %sudo ALL=(ALL) ALL

## Uncomment to allow any user to run sudo if they know the password
## of the user they are running the command as (root by default).
# Defaults targetpw  # Ask for the password of the target user
# ALL ALL=(ALL) ALL  # WARNING: only use this together with 'Defaults targetpw'

## Read drop-in files from /etc/sudoers.d
## (the '#' here does not indicate a comment)
#includedir /etc/sudoers.d

That problem solved strangely,by checking and unchecking Enable administrator privilage for this user, in KDE user manager!!!
actually this add/remove user to the wheel group.

Last edited by clever (2020-03-31 10:27:58)

seth · 2020-03-31 14:28:01

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

eschwartz · 2020-04-01 00:41:18

clever wrote:

and i wrote no custom polkit.

any idea?!

Note that polkit by *default* will permit members of the wheel group to authenticate. This goes together with your discovery that a KDE application was adding and removing you from the wheel group.

Note that org.freedesktop.systemd1.manage-units should be requiring a password even so... the default is a polkit.addAdminRule which simply adds wheel to the list of admins who can be prompted for a password... but WON'T return polkit.Result.YES to auto-allow.

Is it possible something else is writing additional rules in /usr/share/polkit-1/rules.d/ or /etc/polkit-1/rules.d/, e.g. polkit.addRule() sections which allow the wheel group to succeed without a password?

Arch Linux

#1 2020-03-31 09:23:09

[Solved] Weird Security Issue, some critical commands run without pass

#2 2020-03-31 09:33:22

Re: [Solved] Weird Security Issue, some critical commands run without pass

#3 2020-03-31 10:01:12

Re: [Solved] Weird Security Issue, some critical commands run without pass

#4 2020-03-31 14:28:01

Re: [Solved] Weird Security Issue, some critical commands run without pass

#5 2020-04-01 00:41:18

Re: [Solved] Weird Security Issue, some critical commands run without pass

Board footer