About the SVG font manipulation vulnerability that was fixed in 11.52 comments

Page 2 of 2 (55 comments)

Left under the original article, as archived.

Cutting SpoonThursday, October 20, 2011 10:48:13 PM
It's good that you documented what you found in config; however a 'sploit either "works" or "doesn't work". You could add a rule to urlfilter that blocks "*.svg", if the system is functional it should block ALL files of that type from being downloaded as part of a page.
ChrisFriday, October 21, 2011 12:44:06 PM
Your attack won't change the fact that you lied, and pushed someone else's lies as well.
Scott CiFriday, October 21, 2011 3:28:21 PM
Thank you, 'Spork. There are several SVG file extensions/MIME types so I can try adding all of them to URLFilter or just delete them and hope for the best.

As far as I know I don't need SVG so I would prefer an on/off switch that is not exploitable even when it appears to be switched off.

Yes, I do know that an exploit either works or it does not work so the cache, quality, and framerate settings were written tongue-in-cheek.
Cutting SpoonFriday, October 21, 2011 5:07:45 PM
Okay. Like I said, not sure what to tell you. But it's easy enough to check if a few wildcards prevent the file from being loaded in the first place. Beyond that, sure, post on the bug tracker (or in the Desktop Wishlist forum). Good luck.
Scott CiFriday, October 21, 2011 6:44:29 PM
Thank you for your help and the suggestions!