News for hackers. Stuff that matters.
Re:How Gmail’s Image Caching Affects Open Tracking by acgourley on Thursday December 12, 2013 @09:38PM (#6898741)
Why couldn't google show images by default before turning on the cache? I assume it's a security issue, but would be interested to hear the reason in detail.
Re:How Gmail’s Image Caching Affects Open Tracking by patio11 on Thursday December 12, 2013 @09:43PM (#6898759)
Among other reasons, imagine me sending [email protected] an email with <img src="http://localhost:3000/carefully-constructed-url" /> if I knew Example.com was a Rails shop in January 2013. That could have been oodles of fun. localhost:3000 is one of the many, many examples of things that could be put there. Other examples include probing for internal redmine instances, attempting to compromise dev/staging servers which are firewalled from outside traffic, etc etc.

This is not a risk if Google proxies the image -- they'll proxy a 404, because Gmail's servers don't have privileged, cookied access to apps on your internal network, dev boxes, etc.

Re:How Gmail’s Image Caching Affects Open Tracking by cypherpunks01 on Thursday December 12, 2013 @10:33PM (#6898929)
Good point about an outsider potentially poking at internal.corporate.com. Though you could only trick [email protected] into making a GET request in this manner, right? Which ideally doesn't change data, but obviously exposes bigger attack area for vulnerabilities like the rails one.
Re:How Gmail’s Image Caching Affects Open Tracking by kogir on Friday December 13, 2013 @09:23AM (#6900569)
Rails in January 2013 was mentioned specifically because a series of security bugs allowed attackers to achieve remote code execution with specially crafted URL parameters.

Thus someone could get a remote shell on your box running as the rails account, not just access to an internal application.