openssl: Perl crashes in test_sslrecords on Windows 11 due to stack overflow
Device Information
- Processor AMD Ryzen 7 8840HS w/ Radeon 780M Graphics 3.30 GHz
- Installed RAM 16.0 GB (15.3 GB usable)
- System type 64-bit operating system, x64-based processor
Operating System Information
- Edition Windows 11 Home
- Version 24H2
- Installed on 1/19/2025
- OS build 26100.2894
- Experience Windows Feature Experience Pack 1000.26100.36.0
Compiler Information
- Microsoft Visual Studio Community 2019
- Version 16.11.42
- VisualStudio.16.Release/16.11.42+35425.106
- Microsoft .NET Framework
- Version 4.8.09032
- Installed Version: Community
- Microsoft Visual C++ 2019
- Visual Studio Tools for CMake 1.0
Perl Information
- This is perl 5, version 40, subversion 0 (v5.40.0) built for MSWin32-x64-multi-thread
NMake Information
- Microsoft ® Program Maintenance Utility Version 14.29.30157.0
OpenSSL Information
Steps to Expose Bug
- Start the Developer Command Prompt inside Visual Studio.
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvarsall.bat" amd64
cd D:\Projects\openssl
perl Configure VC-WIN64A --prefix=D:/Projects/openssl
nmake
nmake TESTS=test_sslrecords test
Expected Behavior
- The test_sslrecords test case should pass, or at least not crash.
Actual Behavior
- The test_sslrecords test case crashes.
- It causes the Blue Screen of Death.
- Hard reboot required.
Notes
- All other tests passed without crashing. I confirmed that by running this command.
nmake TESTS=-test_sslrecords test
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 30 (13 by maintainers)
so we’re actually crashing inside the test harness code, thats good information, thank you.
This is really starting to seem like an error in the H2 update from windows, as the perl TAP code (I don’t think) has changed (which doesn’t really prove anything, but given that the crash is outside the openssl perl code, I’m left with no other theory at the moment).
see comment here
It looks like perl fixed this with commit 87f42aa0e0096e9a346c9672aa3a0bd3bef8c1dd , which is part of perl 5.41.12. You should update to that version of perl to fix the issue
Note, This just came across my email: https://nvd.nist.gov/vuln/detail/CVE-2024-56406 https://seclists.org/oss-sec/2025/q2/50
Looks like a stack overflow vulnerability has been disclosed in Perl, which this issue may be related to.
Not sure what the release schedule is for fixing it, but its probably worth updating as soon as a new release is announced to see if it mitigates the problem