Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
User with only "Discover Reader" role enabled, is able to get private key for manifest/organization when they authenitcate to the Satellite WEb UI, and then manually navigate to this endpoint:
http://satellite.example.com/katello/api/v2/organizations/1
A json output is printed to the screen which includes the private and public key for what I believe is the manifest associated with that organization. I have grabbed part of the json, and removed the public and private certs, and also hanged the org name and manifest name to ORGANIZATION-NAME and MANIFEST-NAME respectively:
"name": "ORGANIZATION-NAME",
"owner_details": {
"autobindDisabled": false,
"contentAccessMode": "entitlement",
"contentAccessModeList": "entitlement",
"contentPrefix": "/ORGANIZATION-NAME/$env",
"created": "2020-04-03T16:16:09+0000",
"defaultServiceLevel": null,
"displayName": "ORGANIZATION-NAME",
"href": "/owners/ORGANIZATION-NAME",
"id": "8a8080887140d389017140d4085f0001",
"key": "ORGANIZATION-NAME",
"lastRefreshed": "2020-04-04T00:04:44+0000",
"logLevel": null,
"parentOwner": null,
"updated": "2020-04-04T00:04:44+0000",
"upstreamConsumer": {
"apiUrl": "https://subscription.rhsm.redhat.com/subscription/consumers/",
"contentAccessMode": null,
"created": "2020-04-04T00:04:28+0000",
"id": "8a8080887140d38901714280c81a005d",
"idCert": {
"cert": "-----BEGIN CERTIFICATE----***REMOVED***-----END CERTIFICATE-----\n",
"created": "2020-04-03T23:51:05+0000",
"id": "8a8080887140d38901714280c80e005c",
"key": "-----BEGIN RSA PRIVATE KEY----***REMOVED***-----END RSA PRIVATE KEY-----\n",
"serial": {
"collected": false,
"created": "2020-04-03T23:51:05+0000",
"expiration": "2021-04-03T23:51:05+0000",
"id": 6867080507192518295,
"revoked": false,
"serial": 6867080507192518295,
"updated": "2020-04-04T00:04:28+0000"
},
"updated": "2020-04-04T00:04:28+0000"
},
"name": "MANIFEST-NAME",
"ownerId": "8a8080887140d389017140d4085f0001",
"type": {
"id": "8a8080887140d38901714280c7640006",
"label": "satellite",
"manifest": true
},
"updated": "2020-04-04T00:04:28+0000",
"uuid": "4aa39171-de7c-4936-bfd9-b06b27000581",
"webUrl": "access.redhat.com/management/subscription_allocations/"
},
"virt_who": true
},
Version-Release number of selected component (if applicable):
Satellite 6.6.2-1
How reproducible:
Always
Steps to Reproduce:
1. Create user with "Discover Reader" role
2. Have that user log in to the Satellite Web UI
3. Open a new tab, and manually navigate to https://satellite.example.com/katello/api/v2/organizations/1
Actual results:
Private and public key are exposed to end user
Expected results:
User should see private and public key. Also, private key should not be exposed.
Additional info:
Thank you for the report. The good news is that this has already been fixed in our upstream repositories - I've linked the upstream issue report. I would expect this fix to be included as part of Satellite 6.8
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 (Important: Satellite 6.8 release), 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-2020:4366