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:

Satellite 6 doesn't provide a means to search for a erratum based upon a CVE identifier, such as CVE-2014-3145. 

Searching by this very easily gave the ability to determine:
* What Red Hat Security Advisory (RHSA) does this map back to 
* and (most importantly) What systems are affected by the vulnerability

This capability is used very heavily by existing Satellite 5 customers & not having this capability will be seen as a fairly large regression.

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

*** This bug has been marked as a duplicate of bug 1124992 ***

Adding 1124992 as a "depends on" but it's really just related.

Errata can now be searched by CVE, e.g. "cve = CVE-2014-1111"

Fixed upstream in katello|2ef156aad07963f3f19553010d40b67cde7e1866

Verified by QE on version Satellite-6.1.0-RHEL-7-20150331.1

This bug is slated to be released with Satellite 6.1.

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.

https://access.redhat.com/errata/RHSA-2015:1592