Microsoft Security Essentials up to 4.1 Registry memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Microsoft Security Essentials up to 4.1. It has been rated as critical. The impacted element is the function HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Security Client of the component Registry. Performing a manipulation of the argument "UninstallString"="C:\Program Files\Microsoft Security Client\Setup.exe /X" results in memory corruption.
Additionally, an exploit exists.
Upgrading the affected component is advised.
Details
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. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. 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.
The vulnerability is also documented in the vulnerability database at OSVDB (93081†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.3VulDB Meta Temp Score: 8.4
VulDB Base Score: 9.3
VulDB Temp Score: 8.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Upgrade: Security Essentials 4.2
Timeline
02/13/2013 🔍05/04/2013 🔍
05/04/2013 🔍
05/13/2013 🔍
03/20/2019 🔍
Sources
Vendor: microsoft.comAdvisory: seclists.org
Researcher: Stefan Kanthak
Status: Not defined
Coordinated: 🔍
GCVE (VulDB): GCVE-100-8631
OSVDB: 93081
Entry
Created: 05/13/2013 16:41Updated: 03/20/2019 20:38
Changes: 05/13/2013 16:41 (47), 03/20/2019 20:38 (1)
Complete: 🔍
Committer:
Cache ID: 216:13E:103
No comments yet. Languages: en.
Please log in to comment.