Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 470758 - kernel: file caps: always start with clear bprm->caps_*
kernel: file caps: always start with clear bprm->caps_*
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
high Severity high
: ---
: ---
Assigned To: Red Hat Product Security
:
Depends On: 470759
Blocks:
  Show dependency treegraph
 
Reported: 2008-11-09 22:38 EST by Eugene Teo (Security Response)
Modified: 2011-09-30 16:59 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-09-30 16:59:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
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-2009:0053 normal SHIPPED_LIVE Important: kernel-rt security and bug fix update 2009-02-04 10:05:12 EST

  None (edit)
Description Eugene Teo (Security Response) 2008-11-09 22:38:37 EST
Description of problem:
From: Serge Hallyn <serue@us.ibm.com>

While Linux doesn't honor setuid on scripts.  However, it mistakenly
behaves differently for file capabilities.

This patch fixes that behavior by making sure that get_file_caps()
begins with empty bprm->caps_*.  That way when a script is loaded,
its bprm->caps_* may be filled when binfmt_misc calls prepare_binprm(),
but they will be cleared again when binfmt_elf calls prepare_binprm()
next to read the interpreter's file capabilities.
Comment 4 Kurt Seifried 2011-09-30 16:59:16 EDT
This issue has been addressed in following products:

  Red Hat Enterprise MRG v1 for Red Hat Enterprise Linux (version 5)
  
Via RHSA-2009:0053 available at https://rhn.redhat.com/errata/RHSA-2009-0053.html

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