Cross-origin problems caused by CSS like IE8

Yesterday, I heard that twitter was hit by csrf and only effective under IE8, but I never went into details about the cause. After throwing the link to the hi group, I hid in the corner and watched the black pot and discussed it with pz. After a while, I forgot about it. Shu gave this picture today to understand the cross-origin vulnerability POC caused by this css. The Code is the same as the image above. This is simply the Weibo killer. (It seems that no program like Weibo will escape the braces colon, right ?) In theory, var x = document. body. currentStyle. fontFamily; you can save all the content after {} body {font-family: "To x. As for how to use it, you will be wise. Who told me to read others' emails? This vulnerability does seem very retarded .. Wood has advanced techniques, wood has unreadable code .. Who found it? Worship one .. This is a funny cross-origin attack that apparently violates the same-origin policy. Why isn't Internet Explorer alone have this vulnerability? Even IE6 won't have this cross-origin problem. Why? Html "target = _ blank>Stab thisIt is much more detailed.