Bug 98020 - CAN-2003-0388 - Security Advisory 06.16.03: Linux-PAM getlogin() Spoofing Vulnerability
Summary: CAN-2003-0388 - Security Advisory 06.16.03: Linux-PAM getlogin() Spoofing Vul...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: pam
Version: 7.2
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Jay Turner
URL: http://www.idefense.com/advisory/06.1...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-06-25 15:52 UTC by Jesse Throwe
Modified: 2015-01-08 00:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-01-02 10:37:15 UTC
Embargoed:


Attachments (Terms of Use)

Description Jesse Throwe 2003-06-25 15:52:03 UTC
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

iDEFENSE Security Advisory 06.16.03:
http://www.idefense.com/advisory/06.16.03.txt
Linux-PAM getlogin() Spoofing Vulnerability
June 16, 2003

I. BACKGROUND

The Pluggable Authentication Module (PAM) is a flexible mechanism for
authenticating users. More information is available at
http://www.kernel.org/pub/linux/libs/pam/ .

II. DESCRIPTION

The pam_wheel module of Andrew G. Morgan's Linux-PAM uses getlogin() in
an insecure manner, thereby allowing attackers to bypass certain
restrictions. The pam_wheel module is often used with su(1) to allow
users belonging to a trusted group to utilize the command without
supplying a password. The module utilizes the getlogin() function to
determine the name of the currently logged in user. This name is then
compared against a list of members of a trusted group as specified in
the configuration file. The following is a snippet of the offending
section of code: 

fromsu = getlogin();
if (fromsu) {
    tpwd = getpwnam(fromsu);
}

...
...
...

/*
* test if the user is a member of the group, or if the
* user has the "wheel" (sic) group as its primary group.
*/
if (is_on_list(grp->gr_mem, fromsu) || (tpwd->pw_gid == grp->gr_gid)) {
    if (ctrl & PAM_DENY_ARG) {
        retval = PAM_PERM_DENIED;
    } else if (ctrl & PAM_TRUST_ARG) {
        retval = PAM_SUCCESS;        /* this can be a sufficient check
*/
    } else {
        retval = PAM_IGNORE;
    }
} else { 

If the "trust" option is enabled in the pam_wheel configuration file
and the "use_uid" option is disabled, any local user may spoof the
username returned by getlogin() and gain access to a super-user account
without supplying a password. The following is a sample exploitation
scenario:

$ w
10:32am up 3:26, 2 users, load average: 0.01, 0.01, 0.00
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
root tty1 - 7:13am 3:03m 0.30s 0.22s -bash 
farmer pts/0 172.16.60.5 10:32am 0.00s 0.00s ? -

$ logname
farmer

$ ln /dev/tty tty1
$ bash < tty1

$ logname
root

$ su -
# id
uid=0(root) gid=0(root)
groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel) 

III. ANALYSIS

If the appropriate configuration options are enabled, and a member of
the wheel group is currently logged in, any local user can spoof log
entries, or, in the worst case scenario, obtain super-user privileges
depending on the PAM configuration settings.

IV. DETECTION

Linux-PAM 0.77 and previous versions are vulnerable, however, the
necessary configuration for exploitability must also exist. More
specifically, a trust of the wheel group must exist in an application
such as su(1), and the use_uid option must not be enabled. This is
usually not the default situation with most Linux installations.

The following is a sample default nonvulnerable entry from
/etc/pam.d/su in Redhat 7.3:

# Uncomment the following line to implicitly trust users in the "wheel"
group.
#auth sufficient /lib/security/pam_wheel.so trust use_uid

The following is a sample entry in /etc/pam.d/su that would be
vulnerable to the described attack:

# Uncomment the following line to implicitly trust users in the "wheel"
group.
auth sufficient /lib/security/pam_wheel.so trust

V. WORKAORUND

When utilizing the pam_wheel module, enable the use_uid option. Doing
so should prevent the login name spoofing from circumventing PAM
restrictions.

VI. VENDOR FIX

Andrew Morgan does not plan to release a new version of Linux-PAM,
however, Linux-PAM 0.78, which does fix this flaw, is obtainable via
the following CVS:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/pam/Linux-PAM/

Linux distributors will be releasing their own updates as appropriate.

VII. CVE INFORMATION

The Mitre Corp.'s Common Vulnerabilities and Exposures (CVE) Project
has assigned the identification number CAN-2003-0388 to this issue.

VIII. DISCLOSURE TIMELINE

21 OCT 2002      Issue disclosed to iDEFENSE
22 NOV 2002      Andrew Morgan (Linux-PAM maintainer) notified
23 NOV 2002      Response received from Andrew Morgan
25 NOV 2002      iDEFENSE clients notified
14 DEC 2002      Patch provided to iDEFENSE for validation
14 JAN 2003      Issue fixed in CVS
09 JUN 2003      Andrew Morgan contacted re: availability of next 
                 stable release
09 JUN 2003      vendor-sec informed of CVS updates
16 JUN 2003      Coordinated public disclosure

X. CREDIT

Karol Wiesek (appelast.pl) is credited with discovering this
vulnerability.


Get paid for security research
http://www.idefense.com/contributor.html

Subscribe to iDEFENSE Advisories:
send email to listserv, subject line: "subscribe"


About iDEFENSE:

iDEFENSE is a global security intelligence company that proactively
monitors sources throughout the world - from technical vulnerabilities
and hacker profiling to the global spread of viruses and other
malicious code. Our security intelligence services provide
decision-makers, frontline security professionals and network
administrators with timely access to actionable intelligence and
decision support on cyber-related threats. For more information, visit
http://www.idefense.com .

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0

iQA/AwUBPu3bS/rkky7kqW5PEQLIVgCfQyqAETE8GYtZy5Srg67uLsvkE/oAn0zY
ztyfj24MPXXfP3rBcBKnmyEB
=uNkK
-----END PGP SIGNATURE-----

Comment 1 Mark J. Cox 2003-06-26 08:53:29 UTC
This security issues is only a risk to users that are using pam_wheel (which is
not a default in Red Hat Linux) and if they are using in a non-default way (not
the way shown commented out in the configuration file).  Therefore we consider
this of minimal risk and have given it a low priority.  

Comment 2 Mark J. Cox 2003-07-08 18:39:07 UTC
(note this also applies to Red Hat Enterprise Linux)

Comment 3 Mark J. Cox 2003-07-09 10:54:18 UTC
bug 98826 is used for tracking this issue in Red Hat Enterprise Linux


Note You need to log in before you can comment on or make changes to this bug.