VDB-8631 · OSVDB 93081

Microsoft Security Essentials up to 4.1 Registry memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.4$0-$5k0.00

A vulnerability classified as critical has been found in Microsoft Security Essentials up to 4.1. This affects the function HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Security Client of the component Registry. The manipulation of the argument "UninstallString"="C:\\Program Files\\Microsoft Security Client\\Setup.exe /X" with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was released 05/04/2013 by Stefan Kanthak as not defined mailinglist post (Bugtraq). It is possible to read the advisory at seclists.org. The public release was coordinated with Microsoft. The exploitability is told to be difficult. Attacking locally is a requirement. No form of authentication is needed for exploitation. Technical details and a public exploit are known.

After immediately, there has been an exploit disclosed. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $25k-$100k.

Upgrading to version 4.2 eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.

Productinfoedit

Vendor

Name

CPE 2.3infoedit

CPE 2.2infoedit

CVSSv3infoedit

VulDB Meta Base Score: 9.3
VulDB Meta Temp Score: 8.4

VulDB Base Score: 9.3
VulDB Temp Score: 8.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2infoedit

AVACAuCIA
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfoedit

Class: Memory corruption
CWE: CWE-119
ATT&CK: Unknown

Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Price Prediction: 🔍
Current Price Estimation: 🔍

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Threat Intelligenceinfoedit

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfoedit

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍
Exploit Delay Time: 🔍

Upgrade: Security Essentials 4.2

Timelineinfoedit

02/13/2013 🔍
05/04/2013 +80 days 🔍
05/04/2013 +0 days 🔍
05/13/2013 +9 days 🔍
03/20/2019 +2137 days 🔍

Sourcesinfoedit

Vendor: https://www.microsoft.com/

Advisory: seclists.org
Researcher: Stefan Kanthak
Status: Not defined
Coordinated: 🔍
OSVDB: 93081

Entryinfoedit

Created: 05/13/2013 04:41 PM
Updated: 03/20/2019 08:38 PM
Changes: (1) vulnerability_cwe
Complete: 🔍

Comments

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!