Bug 1434106 (CVE-2017-2662) - CVE-2017-2662 foreman: Managing repositories with their id via hammer does not respect the role filters
Summary: CVE-2017-2662 foreman: Managing repositories with their id via hammer does no...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2017-2662
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1410916 1429590 1436931 1436932
Blocks: 1432306
TreeView+ depends on / blocked
 
Reported: 2017-03-20 17:55 UTC by Kurt Seifried
Modified: 2021-04-21 16:46 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-21 16:46:33 UTC


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 18035 0 Normal Closed Should only be able to add repositories you have access to 2020-07-13 15:47:19 UTC
Foreman Issue Tracker 30380 0 Normal New repositories controller does not respect permissions 2020-07-13 15:46:55 UTC

Description Kurt Seifried 2017-03-20 17:55:40 UTC
Brad Buckingham of Red Hat reports:

After settings a new role to allow restricted access on a repository with a filter (filter set on the Product Name), the filter is not respected when the actions are done via hammer using the repository id.

External reference:
http://projects.theforeman.org/issues/18838

Comment 3 Kurt Seifried 2017-07-15 02:03:09 UTC
Acknowledgments:

Name: Brad Buckingham (Red Hat)

Comment 5 errata-xmlrpc 2021-04-21 13:10:16 UTC
This issue has been addressed in the following products:

  Red Hat Satellite 6.8 for RHEL 7

Via RHSA-2021:1313 https://access.redhat.com/errata/RHSA-2021:1313

Comment 6 Product Security DevOps Team 2021-04-21 16:46:33 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2017-2662


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