6 ms·
Exploits in jpg/png are very rare. A major security issue with probably the most popular automated image processing toolkit in existence came to light just the
by Silhouette 11y ago
Exploits in jpg/png are very rare.
A major security issue with probably the most popular automated image processing toolkit in existence came to light just the other day. That particular one would be used for attacking servers, but there have been client-side vulnerabilities in other common resources such as fonts before too. Assuming that just because a format is common the software processing it won't introduce any vulnerabilities is not a great idea.
In any case, the relative rarity isn't really the point. Either it's ethically and/or legally correct to assign blame for malicious advertising to the final host site that the user actually visits, or it isn't. That's the principle we're really debating, and the rest is just a degree of risk.
- Dylan16807 11y ago>A major security issue with probably the most popular automated image processing toolkit in existence came to light just the other day. Because of all the weird formats it supports. That's why I said jpg/png, not 'images'. Any software that supports 200 formats probably has severe bugs on the rare ones. Doesn't matter for making a secure image server where you can dictate the format. >In any case, the relative rarity isn't really the point. Either it's ethically and/or legally correct to assign blame for malicious advertising to the final host site that the user actually visits, or it isn't. That's the principle we're really debating, and the rest is just a degree of risk. Whether they are being negligent is relevant. Allowing known-risky formats that keep failing over and over is negligent.
- Silhouette 11y agoAllowing known-risky formats that keep failing over and over is negligent. But if you look at this from the opposite direction, you're essentially arguing that we should only use technologies that are known, or at least reasonably expected, to be extremely safe. Given that in general humanity hasn't yet figured out how to create such technologies, and that numerous formats we use every day on the web to great overall benefit would not qualify, that seems a tall order.
- Dylan16807 11y ago> But if you look at this from the opposite direction, you're essentially arguing that we should only use technologies that are known, or at least reasonably expected, to be extremely safe. No I'm not. Go ahead and use a new technology. But don't use a proven-bad technology. If you tried a reasonable amount and don't know about security holes, that's one thing. If someone shows you the security holes, and you don't fix them, that is where you're a bad actor.
- Silhouette 11y agoGo ahead and use a new technology. But don't use a proven-bad technology. But the "proven bad" technology you're talking about here is just incorporating any third party content in your site. Obviously that is a security risk if the third party isn't perfect about policing what they host. On the other hand, billions of resources are served in that way every day, and the web is a much better place for it. Only a tiny fraction of those third party resources are hostile, and most of the ones that are will be closed down rapidly by the third party service themselves once discovered. So is this really in "proven bad", "known-risky" territory, or are we actually talking about "very rare" dangers and a lot of hyperbole here?
- Dylan16807 11y agoThe problem is incorporating third party content that is neither screened nor sanitized. The proportion doesn't matter as much as the fact that there is nothing stopping attacks. They only get cleaned up afterwards. You don't expose your users to attack without warning. I think very few websites allow one person to embed arbitrary scripts that will be shown to another person.
- Silhouette 11y agoThe problem is incorporating third party content that is neither screened nor sanitized. It is impossible to screen or sanitize third party content if the third party is hosting it and the user loads it when your page refers to it. The third party can change that content at any time, without your knowledge or consent. This is how almost all ad networks work. It is also how almost all CDNs, web font services, image hosting services, etc. work. I think very few websites allow one person to embed arbitrary scripts that will be shown to another person. Every single site on the web that hosts jQuery via a CDN does exactly that. This single example alone represents many millions of sites.