The researcher, Michal Zalewski
, on June 4 reported
a model for representing HTML or XML and related formats.
The result can be cookie stealing or cookie resetting, browser crash, page hijacking, code injection or memory corruption.
The previous permissions pertain to content for the newly loaded page, which can be malicious, such as:
- Read or set victim.document.cookie
- Arbitrarily alter document DOM, including changing form submission URLs, injecting code
- Read or write DOM structures that were not fully initialized, prompting memory corruption and browser crash.
Zalewski has posted a demo here
Zalewski found another bug, this one of medium impact, having to do with an IE 6 file prompt delay bypass that could lead to a forced download or execution of filesURL bar spoofing. IE 7 isnt affected, he said, due to high-level browser changes. Hes posted a demo here
Microsoft is investigating the two possible vulnerabilities. A spokesperson said that at this point, the company isnt aware of any attacks that have tried to exploit the flaws.
(inline frames) to display contents or store state data
in other words, the unique configuration of information in a program or machineor to communicate with a server.
An IFrame is an HTML element through which one HTML document can be embedded within a main document.
This problem, which Zalewski tags as being a major flaw, can lead to interception of keystrokes and content spoofing, among other things. Mozilla said that the flaw allows attackers to display "offensive, misleading or dangerous contents on trusted sites" or to spoof login prompts. An attacker can also track user behavior, such as timing when a victim arrived and departed at a site, because of the presence of IFrames.
Mozilla also said that this flaw is a duplicate of a previously reported flaw, Bug 381300
on Mozillas bug site by agreeing that the underlying bugs are "very much the same," but that the attack scenario differs from his findings in two ways.
"The initial report considered only a more benign opportunity (page element spoofing vs. snooping on user input), and did not account for the possibility that persistent about:blank frames that do not require a race condition to occur (which is important when considering a proper fix; but that point is moot if you plan to backport a more comprehensive fix from trunk)."
Zalewski has a demo of the Firefox bug here
Check out eWEEK.coms Security Center for the latest security news, reviews and analysis. And for insights on security coverage around the Web, take a look at eWEEKs Security Watch blog.