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.

* Why we should update this gem?

1. To avoid future vulnerabilities (recent example: CVE-2013-0269)
https://bugzilla.redhat.com/show_bug.cgi?id=909029

2. rubygem-json-1.4.6-2.el6 is not supported from upstream now
https://github.com/flori/json/branches


* Satellite server does not ship this gem, Satellite tools repo however has this as a package. All current active and upcoming streams of tools repo ship this: 6.5, 6.6, 6.7 and 6.8.
https://errata.devel.redhat.com/package/show/rubygem-json

The rubygem-json package we ship is only in the RHEL 6 tools repository. Given that https://access.redhat.com/security/cve/CVE-2013-0269 has been deemed not to affect Satellite and there is no active CVE against the package, my recommendation is that we close wontfix this BZ. RHEL 6 has entered ELS phase ending in June 30, 2024.