-
1. Re: Using SQL query to find Q numbers associated with CVE's for WannaCry
cwinning Jun 13, 2017 6:48 AM (in response to Codys26)Hello,
The only addition to my list is Q4013429 which was released in March, was a CVE missed in your script?
Here is more information on the patches for WannaCry: Latest information on WannaCrypt and How to Protect Against It (Shavlik Protect, Patch for Windows Server)
I used an API command in version 9.3 to add patches for CVEs, CVE-2017-0143 through 0148. These were run from administrative Powershell CMD:
Add-PatchGroup -Name 'WannaCry' -Description 'CVE-2017-0143 through 0148'
Add-PatchGroupItem -Name 'WannaCry' -Cve 'CVE-2017-0143','CVE-2017-0144','CVE-2017-0145','CVE-2017-0146','CVE-2017-0147','CVE-2017-0148'
These patches were added a new Patch Group based on the CVEs in the input:
Here is the export of the group:
Q4012212
Q4012213
Q4012214
Q4012215
Q4012216
Q4012217
Q4012598
Q4012598
Q4013429
Q4013429
Thanks,
Charles
-
2. Re: Using SQL query to find Q numbers associated with CVE's for WannaCry
Codys26 Jun 14, 2017 10:25 PM (in response to cwinning) -
3. Re: Using SQL query to find Q numbers associated with CVE's for WannaCry
cwinning Jun 15, 2017 8:01 AM (in response to Codys26)Hello,
I just spot checked a patch that supersedes one of the original patches, MS17-05-2K8. It does include have a different CVE.
We have no control on which CVEs are associated with updates.
Thanks,
Charles
-
4. Re: Using SQL query to find Q numbers associated with CVE's for WannaCry
Codys26 Jun 15, 2017 2:10 PM (in response to cwinning)That is no problem. I wasn't sure if that was something controlled through Shavlik or not.
Thanks!
-
5. Re: Using SQL query to find Q numbers associated with CVE's for WannaCry
cwinning Jun 15, 2017 2:33 PM (in response to Codys26)No worries, glad I could help.
Thanks,
Charles