VDB-84482 · SA21557 · OSVDB 28132

Microsoft Internet Explorer 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.
5.1$0-$5k0.00

Summaryinfo

A vulnerability was found in Microsoft Internet Explorer. It has been declared as critical. This affects an unknown part. Such manipulation leads to memory corruption. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Microsoft Internet Explorer (Web Browser) (version now known). It has been rated as critical. Affected by this issue is some unknown processing. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability.

The weakness was disclosed 08/23/2006 by Dejan Kovacevic, Derek Soeder and Hu Qianwei (Website). The advisory is available at research.eeye.com. The technical details are unknown and an exploit is not available.

Upgrading eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at OSVDB (28132†) and Secunia (SA21557†). The entry VDB-2478 is pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

License

Support

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.1

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

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

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Timelineinfo

08/08/2006 🔍
08/23/2006 +15 days 🔍
08/23/2006 +0 days 🔍
08/23/2006 +0 days 🔍
05/08/2016 +3545 days 🔍
05/07/2019 +1094 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: research.eeye.com
Researcher: Dejan Kovacevic, Derek Soeder, Hu Qianwei
Status: Not defined

GCVE (VulDB): GCVE-100-84482
Secunia: 21557 - Internet Explorer URL Compression Buffer Overflow, Highly Critical
OSVDB: 28132 - Microsoft IE HTTP 1.1 URL Parsing Overflow

See also: 🔍

Entryinfo

Created: 05/08/2016 19:57
Updated: 05/07/2019 12:43
Changes: 05/08/2016 19:57 (47), 05/07/2019 12:43 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!