Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 828447 - CVE-2012-5605 Cloudforms grinder: /var/lib/pulp/cache/grinder directory is world-writeable.
Summary: CVE-2012-5605 Cloudforms grinder: /var/lib/pulp/cache/grinder directory is wo...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Configuration Management
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Pradeep Kilambi
QA Contact: Garik Khachikyan
URL:
Whiteboard:
Depends On:
Blocks: CVE-2012-5605
TreeView+ depends on / blocked
 
Reported: 2012-06-04 18:19 UTC by james labocki
Modified: 2019-09-25 21:09 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Release Note
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 19:46:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1543 0 normal SHIPPED_LIVE Important: CloudForms System Engine 1.1 update 2012-12-05 00:39:57 UTC

Description james labocki 2012-06-04 18:19:23 UTC
Description of problem:
The /var/lib/pulp/cache/grinder directory is world-writeable

Comment 1 Justin Sherrill 2012-06-04 20:23:56 UTC
This might be a blocker of  https://bugzilla.redhat.com/show_bug.cgi?id=813571.  at a minimum it provides more information.

Comment 2 Justin Sherrill 2012-06-04 20:35:07 UTC
Errr, i meant dupe, not blocker.

Comment 3 Mike McCune 2012-06-13 15:31:49 UTC
gofer != grinder so I'd say this isn't a dupe.

Comment 5 Lukas Zapletal 2012-06-26 08:23:42 UTC
We are able to fix this in our installer, but I guess it's better to change this in the RPM itself.

Comment 6 Pradeep Kilambi 2012-07-05 13:12:21 UTC
fixed in grinder in commit 41ae9d47c4e3db84b5637cc6b6bdd001a7bdc47e

after fix:

# ls -ld /var/lib/pulp/cache/grinder/
drwxr-x---. 3 apache apache 4096 Jul  5 09:12 /var/lib/pulp/cache/grinder/

Comment 8 Garik Khachikyan 2012-09-19 11:48:56 UTC
# REOPEN

I have got the grinder version of: grinder-0.0.149-1.el6cf.noarch and it is _not_ fixed.

One can see: 
drwxrwxrwx. 3 apache apache 4096 Sep 19 07:46 /var/lib/pulp/cache/grinder/

Comment 13 Garik Khachikyan 2012-10-03 15:15:50 UTC
# VERIFIED

... and grinder-0.0.150-1.el6cf.noarch has the fix!

now one can see:
---
drwxr-x---. 3 apache apache 4096 Oct  3 11:02 /var/lib/pulp/cache/grinder/
---

checked on:
katello-1.1.12-12.el6cf.noarch
katello-cli-1.1.8-6.el6cf.noarch
grinder-0.0.150-1.el6cf.noarch

Comment 20 errata-xmlrpc 2012-12-04 19:46:28 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, and where to find the updated
files, follow the link below.

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

http://rhn.redhat.com/errata/RHSA-2012-1543.html


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