Can F5 help with the vulnerability in WAZE social-traffic app?
Method: Man-in-the-middle HTTPS Proxy. Ability: Create ghost cars to receive real driver's location broadcast when driving. Create a fake traffic jam. Researchers pointed out WAZE servers did not detect anomaly when in a short period of time, many "cars" were created. Details of vulnerability: http://fusion.net/story/293157/waze-hack/ Welcome any of your thoughts and insights. It seems like web security is more obvious and easier to protect than application security/server-to-server communications.