AnsweredAssumed Answered

Anyone notice strange behavior with Linux QID's?

Question asked by Rusty Qualyz on May 20, 2019

Hello,

 

We noticed today, now that it is report day, that the below Linux QID's got dropped on all of our remediation team reports if they own any Linux assets.  These were published 5/16/2019 and modified 05/17/2019.  Just curious to know if anyone saw the same type of behavior.  We have a dynamic search list that specifically assigns these types of QID's to our Linux team and not to our other remediation teams.

 

QID                      Vulnerability Title
237235        Red Hat Update for kernel (RHSA-2019:1168)
237245        Red Hat Update for wget (RHSA-2019:1228)
237236        Red Hat Update for kernel (RHSA-2019:1169)
237244        Red Hat Update for ruby (RHSA-2019:1235)
237237        Red Hat Update for libvirt (RHSA-2019:1180)
237225        Red Hat Update for qemu-kvm (RHSA-2019:1178)
237234        Red Hat Update for libvirt (RHSA-2019:1177)
237216        Red Hat Update for java-1.8.0-ibm (RHSA-2019:1164)
237152        Red Hat Update for kernel (RHSA-2019:0512)
237102        Red Hat Update for kernel (RHSA-2019:0163)
237064        Red Hat Update for kernel (RHSA-2018:3651)
237182        Red Hat Update for kernel (RHSA-2019:0818)
237197        Red Hat Update for ghostscript (RHSA-2019:1017)

Outcomes