Acting against a malicious file upload is not an easy task. We need to maintain fine balance between security and user experience.
We can still use the traditional ways such as checking content type, file headers, extensions etc. but what about in cases where a code is appended to a file jpg/ png files. The above traditional countermeasures will not work.
So a few countermeasures for such scenarios:
We can still use the traditional ways such as checking content type, file headers, extensions etc. but what about in cases where a code is appended to a file jpg/ png files. The above traditional countermeasures will not work.
So a few countermeasures for such scenarios:
- Similar to how WAF (Web Application Firewalls) work, the application should analyze each part of the file. The file needs to be parsed and look for any malicious hints/ contents such as executable codes containing dangerous functions - system, exec, kill etc. Also, check for existence of encoders such as base64 etc. There's no point of their presence in an innocent image file.
- Another effective method is to crop the image before saving it. Check the code here in Case 3 section of Sanitizing image files. What it basically does is, before saving the file, it does some resizing and then save in jpg format. This leaves out .jar trailers. https://www.owasp.org/index.php/Protect_FileUpload_Against_Malicious_File#Case_n.C2.B03:_Images
- In the specific case where only image the valid input for the application, the application should read from the image table structure about the length of the image and discard anything after that. Thus the jar trailers will be laft out.
We need multi thronged approach to counter any malicious file upload issues as there's no single silver bullet.
Comments