Bug 1061762 - Bad file permissions wrong on 2 files
Summary: Bad file permissions wrong on 2 files
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: redhat-rpm-config
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Panu Matilainen
QA Contact: Michal Trunecka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-05 14:58 UTC by Steve Grubb
Modified: 2014-09-30 23:35 UTC (History)
2 users (show)

Fixed In Version: redhat-rpm-config-9.1.0-62.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 09:35:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Steve Grubb 2014-02-05 14:58:39 UTC
Description of problem:
This package has bad permission on 2 files allowing group root writing. The DISA STIG security settings mandates permissions of 755 or less instead. Not fixing this will cause scanner failures when checking system security settings.

Version-Release number of selected component (if applicable):
redhat-rpm-config-9.1.0-61.el7.noarch

Actual results:
GEN001300: /usr/lib/rpm/redhat/config.guess is 775 should be 0755 or less
GEN001300: /usr/lib/rpm/redhat/config.sub is 775 should be 0755 or less

Comment 1 Panu Matilainen 2014-02-06 08:30:02 UTC
config.{sub|guess} copies tripping up security scanners seems mildly hysterical but sure, there's no reason they need to be 775.

Comment 3 Panu Matilainen 2014-02-07 09:09:24 UTC
Fixed in redhat-rpm-config-9.1.0-62.el7

Comment 5 Steve Grubb 2014-02-07 17:00:45 UTC
Thanks! The reason this is important is we have a number of apps that do not drop supplemental groups and they retain group root. So, anything writable by the root group could be altered by an app that has a security vulnerability that did not drop supplemental groups correctly.

Comment 7 Ludek Smid 2014-06-13 09:35:36 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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