Bug 2189578

Summary: Remove default pre-exec hook directories.
Product: Red Hat Enterprise Linux 8 Reporter: Tom Sweeney <tsweeney>
Component: podmanAssignee: Jindrich Novy <jnovy>
Status: CLOSED ERRATA QA Contact: Yuhui Jiang <yujiang>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 8.9CC: ajia, bbaude, dwalsh, jligon, jnovy, lsm5, mboddu, mheon, pthomas, tsweeney, umohnani
Target Milestone: rcKeywords: Triaged, ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: podman-4.6.1-2.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2189582 2189593 (view as bug list) Environment:
Last Closed: 2023-11-14 15:29:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2189582, 2189593    

Description Tom Sweeney 2023-04-25 15:44:07 UTC
Description of problem:

Currently, Podman searches the directories /usr/libexec/podman/pre-exec-hooks or /etc/containers/pre-exec-hooks on the host machine, and if there are any scripts in those directories, they are run at the startup of the container.  Per RHEL Security Alert, we should not do this.  Instead, we should use a configurable option to allow this to happen or use an environment variable to specify the directory.

The longer-term fix is to add an option somewhere to allow for those directories to be used.  However, given the ZeroDay deadline, for that release, we will be just using the environment variable: PODMAN_PREEXEC_HOOKS_DIR.  If that EnVar is defined, scripts in the specified directory will be run.  If not specified, any scripts found in the suggested directories: /usr/libexec/podman/pre-exec-hooks or /etc/containers/pre-exec-hooks will not be run at the container startup.  


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 12 errata-xmlrpc 2023-11-14 15:29:11 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: container-tools:rhel8 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:6939