Status: CLOSED DUPLICATE of bug 59810
Product: Red Hat Linux
Classification: Retired
Component: shadow-utils (Show other bugs)
8.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
David Lawrence
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-06 00:40 EST by Jan Martinek
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:50:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Martinek 2002-11-06 00:40:02 EST
Description of Problem:

When a new user account is created by using useradd command,
a new empty mailbox is created in /var/spool/mail/newuser
with these permissions:
-rw-rw----   newuser  newgroup 
But if two (or more) users have the same GID, they can read
(and modify) each others mail. 

Version-Release number of selected component (if applicable):
shadow-utils-20000902-12

This is what I found in changelog of shadow-utils:
It probably has something to do with the problem mentioned
above.

* Wed May 23 2001 Bernhard Rosenkraenzer <bero@redhat.com> 20000902-1
  - Create an empty mailspool when creating a user so non-setuid/non-setgid
    MDAs (postfix+procmail) can deliver mail (#41811)

How Reproducible:

every time

Steps to Reproduce:
1. useradd -g users newuser1
2. useradd -g users newuser2
3. Now the newuser1 and newuser2 can read and modify each others mail

Actual Results:
see above

Expected Results:
Even if this is done deliberately, I would expect useradd command
to WARN about this potential security flaw.

Additional Information:
Comment 1 Mark J. Cox (Product Security) 2003-02-11 08:28:39 EST

*** This bug has been marked as a duplicate of 59810 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:50:05 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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