6 - Legacy Systems

Microsoft versions are either under:

  • Ongoing support => Updates released frequently

  • Extended support => Grace period, updates still released

  • End of life => Updates no longer released

End of life OS bring a lot of security issuesL

  • Lack of support from software companies

  • Hardware compatibility issues

  • Security flaws

This is common in medical settings and local government, where the vendor for a critical application goes out of business or no longer provides support for an application, so the organization is stuck running it on a version of Windows XP or even Server 2000/2003.

This page lists the EOL dates for each windows version:

Looking for missing patches

A great thing to do on legacy system is to check patches.

First we check the latest patch:

Then we can use sherlock (https://github.com/rasta-mouse/Sherlock) to find missing software patches for local privilege escalation vulnerabilities.

Windows-Exploit-Suggester

This tool compares a targets patch levels against the Microsoft vulnerability database in order to detect potential missing patches on the target. It also notifies the user if there are public exploits and Metasploit modules available for the missing bulletins.

It requires the 'systeminfo' command output

Usage

First we must install some dependencies:

Then run systeminfo on the target and save the output in a .txt file

Update the windows vulnerabilility database:

This should have created a .xls file YYYY-MM-DD-mssb.xls

Finally we can run windows exploit suggester:

Last updated