Segfault in Windows 11

[Reelix]

Before submitting an issue, please make sure you fully read any potential error messages output and did some research on your own.

Subject of the issue

WPScan segfaults at the end of a run.

Your environment

• Version of WPScan: 2.8.22
• Version of Ruby: ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x64-mingw-ucrt]
• Operating System (OS): Windows 11 22H2 (OS Build: 22621.819)

Steps to reproduce

Run wpscan --help

Expected behavior

WPScan exits gracefully.

Actual behavior

WPScan ends with

        --password-attack ATTACK                  Force the supplied attack to be used rather than automatically determining one.
                                                  Available choices: wp-login, xmlrpc, xmlrpc-multicall
        --login-uri URI                           The URI of the login page if different from /wp-login.php
        --stealthy                                Alias for --random-user-agent --detection-mode passive --plugins-version-detection passive

[!] To see full list of options use --hh.
C:/Ruby31-x64/bin/wpscan: [BUG] Segmentation fault
ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x64-mingw-ucrt]

-- C level backtrace information -------------------------------------------
C:\WINDOWS\SYSTEM32\ntdll.dll(NtWaitForSingleObject+0x14) [0x00007fff2630ee84]
C:\WINDOWS\System32\KERNELBASE.dll(WaitForSingleObjectEx+0x8e) [0x00007fff23bc9afe]
C:\Ruby31-x64\bin\x64-ucrt-ruby310.dll(rb_vm_bugreport+0x29e) [0x00007ffe42a6b5ae]
C:\Ruby31-x64\bin\x64-ucrt-ruby310.dll(rb_bug_for_fatal_signal+0x88) [0x00007ffe42863d18]
C:\Ruby31-x64\bin\x64-ucrt-ruby310.dll(rb_fiber_scheduler_address_resolve+0x2be) [0x00007ffe429bbffe]
 [0x00007ff7c83c1f32]
C:\WINDOWS\System32\ucrtbase.dll(_C_specific_handler+0xa0) [0x00007fff236e7f30]
C:\WINDOWS\SYSTEM32\ntdll.dll(_chkstk+0x12f) [0x00007fff26313eaf]
C:\WINDOWS\SYSTEM32\ntdll.dll(RtlFindCharInUnicodeString+0xa96) [0x00007fff2628eae6]
C:\WINDOWS\SYSTEM32\ntdll.dll(KiUserExceptionDispatcher+0x2e) [0x00007fff26312e9e]
 [0x00007ffe423c6fe0]
C:\WINDOWS\System32\ucrtbase.dll(_sys_nerr+0x2b3) [0x00007fff236f3a83]
C:\WINDOWS\System32\ucrtbase.dll(o_free+0xde) [0x00007fff236c006e]
C:\WINDOWS\System32\ucrtbase.dll(execute_onexit_table+0x3d) [0x00007fff236bda1d]
C:\WINDOWS\System32\ucrtbase.dll(exit+0x1a6) [0x00007fff236bbc06]
C:\WINDOWS\System32\ucrtbase.dll(exit+0x14a) [0x00007fff236bbbaa]
C:\WINDOWS\System32\ucrtbase.dll(exit+0x267) [0x00007fff236bbcc7]
 [0x00007ff7c83c14a5]
 [0x00007ff7c83c14e6]
C:\WINDOWS\System32\KERNEL32.DLL(BaseThreadInitThunk+0x1d) [0x00007fff259c244d]

What have you already tried

Tell us what you have already tried to do to fix the issue you are having.

Things you have tried (where relevant):

• Update WPScan to the latest version [✓]
• Update Ruby to the latest version [✓]
• Ensure you can reach the target site using cURL [✓]
• Proxied WPScan through a HTTP proxy to view the raw traffic [✗]
• Ensure you are using a supported Operating System (Linux and macOS) [✗]

Note: WPScan works fine when run using the associated docker container (wpscanteam/wpscan).