Bug 137445 - CAN-2002-0875 filename disclosure in FAM
Summary: CAN-2002-0875 filename disclosure in FAM
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: fam   
(Show other bugs)
Version: 2.1
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact:
Whiteboard: impact=low,public=20020103
Keywords: Security
Depends On:
TreeView+ depends on / blocked
Reported: 2004-10-28 15:28 UTC by Josh Bressers
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-01-05 15:41:13 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:005 normal SHIPPED_LIVE Low: fam security update 2005-01-05 05:00:00 UTC

Description Josh Bressers 2004-10-28 15:28:24 UTC
Vulnerability in FAM 2.6.8, 2.6.6, and other versions allows
unprivileged users to obtain the names of files whose access is
restricted to the root group.

The SGI bugzilla has a patch.


Comment 1 Daniel Veillard 2004-10-28 16:10:12 UTC
2 security advisory in 2 days :-( ... I hope the patch for 2.6.6 
and 2.6.8 will apply okay for 2.6.4 !
Are you sure RHEL3 is not vulnerable since it uses 2.6.8 ?


Comment 2 Josh Bressers 2004-10-28 16:21:57 UTC
This issue is really old, so it's not really accurate to say 2
advisories in 2 days :)

I just checked the source in RHEL3, it's safe.  This only affects RHEL2.1.

Comment 4 Josh Bressers 2005-01-05 15:41:13 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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