Microsoft Internet Explorer 6.0.2900 location memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $25k-$100k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Microsoft Internet Explorer 6.0.2900. The affected element is an unknown function. This manipulation of the argument location causes memory corruption. This vulnerability is tracked as CVE-2006-0830. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as critical was found in Microsoft Internet Explorer 6.0.2900 (Web Browser). Affected by this vulnerability is an unknown code. The manipulation of the argument location with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The scripting engine in Internet Explorer allows remote attackers to cause a denial of service (resource consumption) and possibly execute arbitrary code via a web page that contains a recurrent call to an infinite loop in Javascript or VBscript, which consumes the stack, as demonstrated by resetting the "location" variable within the loop.
The weakness was disclosed 02/21/2006 by porkythepig as not defined posting (Bugtraq). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2006-0830 since 02/21/2006. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $25k-$100k at the moment (estimation calculated on 04/07/2017). It is expected to see the exploit prices for this product decreasing in the near future.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (24788) and SecurityFocus (BID 16687†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Support
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.4
VulDB Base Score: 7.3
VulDB Temp Score: 6.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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Unproven
EPSS Score: 🔍
EPSS Percentile: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/16/2006 🔍02/21/2006 🔍
02/21/2006 🔍
02/21/2006 🔍
03/12/2015 🔍
04/07/2017 🔍
Sources
Vendor: microsoft.comAdvisory: securityfocus.com⛔
Researcher: porkythepig
Status: Not defined
CVE: CVE-2006-0830 (🔍)
GCVE (CVE): GCVE-0-2006-0830
GCVE (VulDB): GCVE-100-28837
X-Force: 24788 - Microsoft Internet Explorer Script Engine stack denial of service
SecurityFocus: 16687 - Microsoft Internet Explorer Script Engine Buffer Overflow Vulnerability
Entry
Created: 03/12/2015 11:11Updated: 04/07/2017 12:08
Changes: 03/12/2015 11:11 (53), 04/07/2017 12:08 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.