A specially crafted web-page can cause Microsoft Internet Explorer 8 to attempt to read data beyond the boundaries of a memory allocation. The issue does not appear to be easily exploitable.
Microsoft Internet Explorer 8
An attacker would need to get a target user to open a specially crafted web-page. Disabling Javascript should prevent an attacker from triggering the vulnerable code path.
The issue requires rather complex manipulation of the DOM and results in reading a value immediately following an object. The lower three bits of this value are returned by the function doing the reading, resulting in a return value in the range 0-7. After exhaustively skipping over the read AV and having that function return each value, no other side effects were noticed. For that reason I assume this issue is hard if not impossible to exploit and did not investigate further. It is still possible that there may be subtle effects that I did not notice that allow exploitation in some form or other.
This report was generated using a predecessor of BugId, a Python script created to detect, analyze and id application bugs. Don't waste time manually analyzing issues and writing reports but try BugId out yourself today! You'll get even better reports than this one with the current version. BugId report: mshtml.id: mshtml.dll!SRunPointer:: RunType Arbitrary~F10 AVR(6045E7D8) description: Security: Attempt to read from unallocated arbitrary memory (@0x0E42CF10) in mshtml. dll!SRunPointer:: RunType note: Based on this information, this is expected to be a security issue!
This report was generated using a predecessor of BugId, a Python script created to detect, analyze and id application bugs. Don't waste time manually analyzing issues and writing reports but try BugId out yourself today! You'll get even better reports than this one with the current version.id: mshtml.dll!SRunPointer:: SpanQualifier Arbitrary~F10 AVR(F5C086DB) description: Security: Attempt to read from unallocated arbitrary memory (@0x0B50DF10) in mshtml. dll!SRunPointer:: SpanQualifier note: Based on this information, this is expected to be a security issue!