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.
DescriptionChristian Marineau
2018-01-12 02:26:33 UTC
Created attachment 1380261[details]
CVEs = N/A
Description of problem:
When looking for Erratas related to Security, we actually can't rely on the CVE number as the "CVEs" field is often set to "N/A".
This is preventing the user from searching using a CVE number. By example, the following will not return any result:
cve = CVE-2017-5715
But this one would return the proper Errata:
cve = CVE-2017-12173
Version-Release number of selected component (if applicable):
6.2
How reproducible:
100%
Steps to Reproduce:
1. Navigate to Content > Errata
2. In the Search field, search for a Security Advisory with type of security:
type = security
3. On the list of results, navigate to show the Errata details. Some of them will have a CVE specified, but the majority of them will have it set to "N/A"
Expected results:
Have the CVE specified 100% of the time to increase the efficiency of the Errata management and help users maintain a more secure environment.
Additional info:
By example, this Errata "RHSA-2018:0012" has no CVE attached, but this one has "RHSA-2017:3379".