0

When I am installing Java 8 on linux system ,Iam getting below error- sudo: effective uid is not 0, is sudo installed setuid root? Please help in this. Below is the sudoer file of system.Please help.

/>mv /usr/lib/java-1.8.0/jdk1.8.0_161 /usr/lib/java />sudo update-alternatives --install "/usr/bin/java" "java" "/usr/lib/jdk1.8.0_161/bin/java" 1 sudo: effective uid is not 0, is sudo installed setuid root? />ls -l $(which sudo) -rwxrwxrwx. 1 root root 123832 Oct 15 2014 /usr/bin/sudo />chmod u+s /usr/bin/sudo chmod: changing permissions of `/usr/bin/sudo': Operation not permitted />

 />mv /usr/lib/java-1.8.0/jdk1.8.0_161 /usr/lib/java
    />sudo update-alternatives --install "/usr/bin/java" "java" "/usr/lib/jdk1.8.0_161/bin/java" 1
    sudo: effective uid is not 0, is sudo installed setuid root?
    />ls -l $(which sudo)
    -rwxrwxrwx. 1 root root 123832 Oct 15  2014 /usr/bin/sudo
    />chmod u+s /usr/bin/sudo
    chmod: changing permissions of `/usr/bin/sudo': Operation not permitted
    />
Sudoer File
## Sudoers allows particular users to run various commands as
## the root user, without needing the root password.
##
## Examples are provided at the bottom of the file for collections
## of related commands, which can then be delegated out to particular
## users or groups.
##
## This file must be edited with the 'visudo' command.

## Host Aliases
## Groups of machines. You may prefer to use hostnames (perhaps using
## wildcards for entire domains) or IP addresses instead.
# Host_Alias     FILESERVERS = fs1, fs2
# Host_Alias     MAILSERVERS = smtp, smtp2

## User Aliases
## These aren't often necessary, as you can use regular groups
## (ie, from files, LDAP, NIS, etc) in this file - just use %groupname
## rather than USERALIAS
# User_Alias ADMINS = jsmith, mikem


## Command Aliases
## These are groups of related commands...

## Networking
# Cmnd_Alias NETWORKING = /sbin/route, /sbin/ifconfig, /bin/ping, /sbin/dhclient, /usr/bin/net, /sbin/iptables, /usr/bin/rfcomm, /usr/bin/wvdial, /sbin/iwconfig, /sbin/mii-tool

## Installation and management of software
# Cmnd_Alias SOFTWARE = /bin/rpm, /usr/bin/up2date, /usr/bin/yum

## Services
# Cmnd_Alias SERVICES = /sbin/service, /sbin/chkconfig

## Updating the locate database
# Cmnd_Alias LOCATE = /usr/bin/updatedb

## Storage
# Cmnd_Alias STORAGE = /sbin/fdisk, /sbin/sfdisk, /sbin/parted, /sbin/partprobe, /bin/mount, /bin/umount

## Delegating permissions
# Cmnd_Alias DELEGATING = /usr/sbin/visudo, /bin/chown, /bin/chmod, /bin/chgrp

## Processes
# Cmnd_Alias PROCESSES = /bin/nice, /bin/kill, /usr/bin/kill, /usr/bin/killall

## Drivers
# Cmnd_Alias DRIVERS = /sbin/modprobe

# Defaults specification

#
# Disable "ssh hostname sudo <cmd>", because it will show the password in clear.
#         You have to run "ssh -t hostname sudo <cmd>".
#
Defaults    requiretty

#
# Refuse to run if unable to disable echo on the tty. This setting should also be
# changed in order to be able to use sudo without a tty. See requiretty above.
#
Defaults   !visiblepw

#
# Preserving HOME has security implications since many programs
# use it when searching for configuration files. Note that HOME
# is already set when the the env_reset option is enabled, so
# this option is only effective for configurations where either
# env_reset is disabled or HOME is present in the env_keep list.
#
Defaults    always_set_home

Defaults    env_reset
Defaults    env_keep =  "COLORS DISPLAY HOSTNAME HISTSIZE INPUTRC KDEDIR LS_COLORS"
Defaults    env_keep += "MAIL PS1 PS2 QTDIR USERNAME LANG LC_ADDRESS LC_CTYPE"
Defaults    env_keep += "LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES"
Defaults    env_keep += "LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE"
Defaults    env_keep += "LC_TIME LC_ALL LANGUAGE LINGUAS _XKB_CHARSET XAUTHORITY"

#
# Adding HOME to env_keep may enable a user to run unrestricted
# commands via sudo.
#
# Defaults   env_keep += "HOME"

Defaults    secure_path = /sbin:/bin:/usr/sbin:/usr/bin

## Next comes the main part: which users can run what software on
## which machines (the sudoers file can be shared between multiple
## systems).
## Syntax:
##
##      user    MACHINE=COMMANDS
##
## The COMMANDS section may have other options added to it.
##
## Allow root to run any commands anywhere
root    ALL=(ALL)       ALL

## Allows members of the 'sys' group to run networking, software,
## service management apps and more.
# %sys ALL = NETWORKING, SOFTWARE, SERVICES, STORAGE, DELEGATING, PROCESSES, LOCATE, DRIVERS
## Allows people in group wheel to run all commands
# %wheel        ALL=(ALL)       ALL

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

## Allows members of the users group to mount and unmount the
## cdrom as root
# %users  ALL=/sbin/mount /mnt/cdrom, /sbin/umount /mnt/cdrom

## Allows members of the users group to shutdown this system
# %users  localhost=/sbin/shutdown -h now

## Read drop-in files from /etc/sudoers.d (the # here does not mean a comment)
#includedir /etc/sudoers.d
Type  :quit<Enter>  to exit Vim
3
  • it looks like you do not have the permission to do this operation via sudo can show us your sudoers file? or can you just su - root? sudo su - root? And do your installation? Commented Mar 15, 2018 at 6:45
  • I have added the sudoer file above and when running sudo su - root getting the same error- />su -root su: invalid option -- 'r' Try `su --help' for more information. />sudo su -root sudo: effective uid is not 0, is sudo installed setuid root? Commented Mar 15, 2018 at 7:15
  • />su - Password: su: cannot set groups: Operation not permitted /> Commented Mar 15, 2018 at 8:14

1 Answer 1

0

Your sudo permissions look suspicious to me:

-rwxrwxrwx. 1 root root 123832 Oct 15  2014 /usr/bin/sudo

Basically that means, anyone can write to it. To me this looks like a vulnerability. I observed file permissions for the sudo executable like the following:

-rwsr-xr-x (MacOS)
-r-s--x--x (FreeBSD)
---s--x--x. (CentOS 7)

Are you sure your system is intact and not compromised?

To change the file permissions on your sudo, I guess you have to login as root (use the su command and your root password) like so:

su root -c chmod u+s /usr/bin/sudo

But this only cures the symptom, you should check your system.

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.