Microsoft Internet Explorer 3.02/4.0/4.01 mk: Protocol Long URL memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Microsoft Internet Explorer 3.02/4.0/4.01. The affected element is an unknown function of the component mk: Protocol Handler. The manipulation as part of Long URL leads to memory corruption. This vulnerability is documented as CVE-1999-1094. The attack can be initiated remotely. There is not any exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Microsoft Internet Explorer 3.02/4.0/4.01 (Web Browser). This issue affects an unknown code of the component mk: Protocol Handler. The manipulation as part of a Long URL 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 summary by CVE is:
Buffer overflow in Internet Explorer 4.01 and earlier allows remote attackers to execute arbitrary commands via a long URL with the "mk:" protocol, aka the "MK Overrun security issue."
The weakness was released 12/31/1999 as confirmed knowledge base article (Website). It is possible to read the advisory at support.microsoft.com. The identification of this vulnerability is CVE-1999-1094. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 5.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at X-Force (917). marc.theaimsgroup.com is providing further details. Entries connected to this vulnerability are available at VDB-15194 and VDB-15219. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: Not defined
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Internet Explorer 5.0
Timeline
12/31/1999 🔍12/31/1999 🔍
06/22/2014 🔍
04/20/2026 🔍
Sources
Vendor: microsoft.comAdvisory: support.microsoft.com
Status: Confirmed
CVE: CVE-1999-1094 (🔍)
GCVE (CVE): GCVE-0-1999-1094
GCVE (VulDB): GCVE-100-15131
X-Force: 917 - Microsoft Internet Explorer MK overrun
Misc.: 🔍
See also: 🔍
Entry
Created: 06/22/2014 16:50Updated: 04/20/2026 03:31
Changes: 06/22/2014 16:50 (44), 04/07/2017 12:06 (12), 04/20/2026 03:31 (15)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.