Here is Liu Die Yu's post to bugtraq explaining this issue.
All mentioned resources can be found at Umbrella.MX.TC
This file is collected and re-edited by Umbrella.MX.TC

________________________[FILE START]________________________

BackMyParent:Son can be bad.

[tested]
Browser Ver
{
MS Internet Explorer: 6.0.2600.0000.xpclnt_qfe.021108-2107;
Encryption: 128-bit;
Patch:; Q810847;
}
(So, it's far from fully patched. It also works after applying the patch for method caching attack.)
OS Ver: "Windows XP Cn ver"

[demo]
http://www.safecenter.net/liudieyu/BackMyParent/BackMyParent-MyPage.HTM
or
http://umbrella.mx.tc
---> BackMyParent section
---> BackMyParent-MyPage file

[exp]
If javascript-protocol Url is left in history, pressing backbutton can get javascript in the javascript-protocol Url executed.
So, two parts:
A.javascript-protocol Url is left in the history list.
B."[VictimWindow].history.back()".

Key:
A:refer to "WsOpenJpuInHistory" at umbrella.mx.tc;
B:top window and its frames/iframes share the same "history" object. so we only have to conquer its frame/iframe.
So one way to do "history.back()" is:
Navigate frame/iframe in the victim window to my document which executes "history.back()" for many times.

[how]
special thanks to:
"Andreas Sandblad" for "Using the backbutton in IE is dangerous";
"Georgi Guninski" for "Default IE 5.0 security settings allow frame spoofing";
and myself :-)


it's very natural. just read those documents.

[greetings]
the Pull, dror, guninski, sandblad and "Friedrich L.Bauer".
of course, mom and dad.

best wishes

-----
from http://Umbrella.MX.TC on http://SafeCenter.NET