This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis β
Q1What is this vulnerability? (Essence + Consequences)
π¨ **Essence**: IE fails to init JS `Window()` with `<BODY onload>`. π₯ **Consequence**: Crash via `CALL DWORD [ECX+8]`. Unicode string 'OBJECT' corrupts ECX (0x006F005B).
Q2Root Cause? (CWE/Flaw)
π‘οΈ **Flaw**: Resource Management Error. π **CWE**: Not specified in data. β οΈ **Root**: Improper initialization of JavaScript objects leading to invalid memory access.
Q3Who is affected? (Versions/Components)
π **Target**: Microsoft Internet Explorer (IE). π₯οΈ **OS**: Windows. π **Pub**: June 1, 2005. π¦ **Vendor**: Microsoft.
Q4What can hackers do? (Privileges/Data)
π **Action**: Trigger Exception/Crash. π **Data**: Potential arbitrary code execution via ECX corruption. π― **Goal**: Denial of Service or Remote Code Execution.
Q5Is exploitation threshold high? (Auth/Config)
π **Auth**: None required. π **Config**: Victim must visit malicious page with specific `<BODY onload>` trigger. π **Threshold**: Low (Remote).
Q6Is there a public Exp? (PoC/Wild Exploitation)
π **PoC**: Yes, referenced in BID 13799 & Secunia 18064. π **Wild Exp**: Historical exploit exists (2005). π **Current**: Low risk today due to age.
Q7How to self-check? (Features/Scanning)
π **Check**: Scan for IE versions on Windows. π **Signatures**: Check OVAL defs (1299, 1303, 1489). π§ͺ **Test**: Use BID 13799 reference for validation.
π« **Workaround**: Disable JavaScript. π **Block**: Use modern browser. π΅ **Network**: Filter malicious HTML payloads at proxy.
Q10Is it urgent? (Priority Suggestion)
β οΈ **Priority**: Low for modern systems. π **Urgency**: Critical in 2005. π‘οΈ **Advice**: Migrate away from IE immediately. π« **Risk**: Minimal if updated.