{'fraction_non_alphanumeric': 0.020813623462630087, 'fraction_numerical': 0.004730368968779565, 'mean_word_length': 5.782051282051282, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Observation of recent Microsoft Zero-Day vulnerabilities

Zero-Day vulnerabilities are an intriguing and ever increasing problem. Microsoft has been one of the more exploited companies having Zero-Day vulnerabilities. This paper intends to identify some relationships within the Zero-Day vulnerabilities identified in nineteen news articles from 2010. We tried to collect data on vulnerability report date, attack report date, vulnerability patch date, vulnerability life cycle category, exploit implemented, Microsoft product affected, and affected functionality. Based on these data, we analyzed the duration between vulnerability notification date and attack date, the distribution of different vulnerability life cycle categories, the most common Microsoft product affected, and the most common exploitation technique used. Our data shows that Potential for Attacks is the most common vulnerability life cycle category, Windows XP SP3 is the most affected system, and the most common exploitation technique is by using malicious code without user input.