[SERVER-44572] Windows null pointer read access violation in SSLHandshakeManager::doServerHandshake Created: 12/Nov/19 Updated: 19/Feb/20 Resolved: 19/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Shane Harvey | Assignee: | Mark Benvenuto |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Sprint: | Security 2019-12-02 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
Very similar to Standalone Windows version:
The server is crashing when the Python driver attempts to connect with this error:
This is consistently happening in our Evergreen CI, for example: https://evergreen.mongodb.com/task/mongo_python_driver_tests_windows_vs2015_python_version_27plus__platform~windows_vs2015_auth_ssl~auth_ssl_python_version~win_vs2015_2.7_test_latest_standalone_9cf0fbd785086ef1702bbafd2ad92a279fe406e4_19_11_08_19_48_15 The full mongo-orchestration log file (which includes the full mongod log) is here: mongo_python_driver_tests_windows_vs2015_python_version_27plus__platform_windows_vs2015_auth_ssl_auth_ssl_python_version_win_vs2015_2.7_test_latest_standalone_9cf0fbd785086ef1702bbafd2ad92a279fe406e4_19_11_08_19_48_15-0-orchestration.log.txt |
| Comments |
| Comment by Mark Benvenuto [ 19/Feb/20 ] |
|
MongoDB 4.4 is not supported on pre-Windows 10 and is now prohibited from running on pre-Windows 10 with |
| Comment by Mark Benvenuto [ 27/Nov/19 ] |
|
As I told Shane over Slack, the reason why mongod.exe is crashing is because SslGetServerIdentity (added in Windows 8) does not exist on Windows 2008 R2. MongoDB no longer supports running on Windows 2008R2. It has a minimum requirement of Windows 10/Windows 2016. I will need to have discussions with people about how and when to enforce the minimum is now Windows 10. |
| Comment by Carl Champain (Inactive) [ 12/Nov/19 ] |
|
Hi shane.harvey, Passing this ticket along to the Security team. |