Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1346051 - (CVE-2016-4982) CVE-2016-4982 authd insecure /etc/ident.key file creation
CVE-2016-4982 authd insecure /etc/ident.key file creation
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20160613,reported=2...
: Security
Depends On: 1346052
Blocks: 1346019 1349160
  Show dependency treegraph
 
Reported: 2016-06-13 15:10 EDT by Kurt Seifried
Modified: 2016-12-13 05:07 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-12-13 05:07:15 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 Kurt Seifried 2016-06-13 15:10:02 EDT
Kurt Seifried of Red Hat reports:

The authd rpm creates the /etc/ident.key file using the following rpm postinstall script:

/usr/bin/openssl rand -base64 -out /etc/ident.key 32
echo CHANGE THE LINE ABOVE TO A PASSPHRASE >> /etc/ident.key
/bin/chown ident:ident /etc/ident.key
chmod o-rw /etc/ident.key

this can lead to the contents of the file being exposed between the time the file is created and the chmod command runs. I would suggest setting umask 077 first. 

Additionally this secret value needs to be unique per instance or install but this value is created at install-time and not during the first run. All container and image instances created would share the same password as this password is set at rpm install time, and each instance should recieve a unique password. 

This bug is being file because Product Security considers "first run problems" to be bugs with the source package and with the container or image only in the aggregate. This view is in collaboration with upstream Fedora. See: https://fedorahosted.org/fpc/ticket/506

The recommended resolution for services is to follow the "First-time Service Setup" pattern (see: https://fedoraproject.org/wiki/Packaging:Initial_Service_Setup ). Other packages may should use a runtime check and generation or similar procedure.
Comment 1 Kurt Seifried 2016-06-13 15:10:10 EDT
Acknowledgments:

Name: Kurt Seifried (Red Hat)
Comment 2 Kurt Seifried 2016-06-13 15:12:02 EDT
Created authd tracking bugs for this issue:

Affects: fedora-all [bug 1346052]

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