Totally Zenned
- Join Date:
- Jul 2012
- Posts:
- 16,908
- Plugin Contributions:
- 2
Image Handler 4 (for v1.5.x) Support Thread
mydanilo:
Applied all the suggested fixes to the code and all seems to work fine. What's next? Can somebody confirm that this does plug the outlined security holes?
For those just tuning in: the security hole being discussed related to a template file that was used in some versions of IH4 to display the additional images. The specific security issue was known as XSS (Cross Site Scripting) which is, in my summary, a situation where the code of one site can be or does use or access the code of another site via a function call from outside the code. In this case, a verification of existence of a local version (file) of the file/pathname combination sent to the template file shows a specific default image if the file/pathname doesn't equal a local item. If it is local, then the file/pathname is sent to be processed as an image.
So that is why it can be said that the correction addresses the XSS concern. Now IH provides a local filename when handling an image and before displaying the image, there is a verification that the image path is local.