Bug 1533713 - CVEs field in Errata is not constantly being populated
Summary: CVEs field in Errata is not constantly being populated
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Errata Management
Version: 6.2.13
Hardware: All
OS: Linux
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On: 1534537
Blocks: CEE_Sat6_Top_BZs, GSS_Sat6_Top_Bugs
TreeView+ depends on / blocked
 
Reported: 2018-01-12 02:26 UTC by Christian Marineau
Modified: 2022-03-13 14:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-17 21:02:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
CVEs = N/A (18.77 KB, image/png)
2018-01-12 02:26 UTC, Christian Marineau
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3320861 0 None None None 2018-01-16 20:03:23 UTC

Description Christian 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".


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