AnsweredAssumed Answered

TLS implementations may disclose side channel information via discrepancies between valid and invalid PKCS#1 padding, and may therefore be vulnerable to Bleichenbacher-style attacks.. This attack is known as a "ROBOT attack

Question asked by Secroa vy on Dec 14, 2017
Latest reply on Dec 18, 2017 by Busby

Request for clarification on the “TLS implementations may disclose side channel information via discrepancies between valid and invalid PKCS#1 padding, and may therefore be vulnerable to Bleichenbacher-style attacks.. This attack is known as a "ROBOT attack".

 

Below steps followed to schedule the report.

  1. Created a search list for the QID found for the below CVEs as per updated QIDs from Qualys.
    1. CVE-2017-6168 CVE-2017-1000385 CVE-2017-17427 CVE-2017-13098 CVE-2017-13099 CVE-2017-17428 CVE-2017-17382 CVE-2012-5081 CVE-2016-6883
  2. Created a patch template with
    1.  FINDINGS - QID based patch evaluation (new)
    2. Asset Groups – All(Except Cloud based asset groups such as Azure, ICHS)
    3. IP Range – All
    4. SORTING and GROUPING by – Host
    5. Display patch severity by: Assigned severity
    6. Filter: Custom- added search list
    7. Access- Empty

 

And scheduled the report.

My reason for this email is when I pulled the report from asset veiw by CVE  found 383 hosts. But by scheduling the report we are getting only 57 hosts.

 

I would like to understand where I have gone wrong if? My Assumption is Asset Veiw is giving Asset report than Patch report required to patch.

Outcomes