Crash in strings v2.53 with interactive EULA prompt

Samuel Leslie 1 Reputation point
2021-01-05T03:33:29.417+00:00

Open a Command Prompt (not PowerShell) and run something like:
strings.exe C:\Windows\System32\notepad.exe > notepad.txt

If the EULA has not been accepted the program will crash immediately after accepting it. Declining will not cause a crash, while running the above sample in PowerShell also doesn't cause a crash; the EULA is simply redirected to the given file instead of interactively prompting.

The issue occurs both with strings.exe and strings64.exe and appears to be a stack buffer overrun. Tested on Windows Server 2012 R2 x64 and Windows 10 20H2 x64. If you've already accepted the EULA simply delete the registry key HKCU\Software\Sysinternals\Strings to be prompted again.

Sysinternals
Sysinternals
Advanced system utilities to manage, troubleshoot, and diagnose Windows and Linux systems and applications.
1,093 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. mariora 376 Reputation points
    2021-01-05T14:23:35.507+00:00

    I can confirm it happens also on Windows server 2019.

    Please file a bug report and send it to syssite@microsoft.com with the steps to repro just like you described them here..

    Thanks
    -mario