3 ms·
Seems like one solution would be to require users uploading images to remove metadata themselves before uploading. The website could reject images that contain
by 1vuio0pswjnm7 5y ago
Seems like one solution would be to require users uploading images to remove metadata themselves before uploading. The website could reject images that contain matadata.
Was Gitlab was extracting the metadata and using it for some purpose. If not, what is the reason to accept images with metadata. Perhaps they assume their customers prefer less "security" and more "convenience", instead of vice versa (less "convenience", more "security").
- Scaevolus 5y agoTheoretically the pure-perl implementation will be immune to most categories of exploits that sloppy binary parsing runs into-- buffer overflows, use after frees, and so on. That better security goes out the window once you start using eval(), of course.
- 1vuio0pswjnm7 5y agoBoth exiv2 and jhead, as examples, have had numerous such bugs. However, there is a difference IMO between running these programs on one's own images (created by oneself), e.g., before uploading them to the internet, versus running them on untrusted images from others.
- Gigachad 5y agoHow do you reject an image that has metadata without doing basically exactly the same process as removing the data?
- 1vuio0pswjnm7 5y agoexiftool does not remove djvu metadata.