HTTPS protocol can be turned into a tracking feature
Get a powerful Linux Dual-Core dedicated server for less than $2.67 a day!Tweet Share on Twitter.
January 6, 2015
A British security consultant has demonstrated how a feature of the secure Web protocol HTTPS can be turned into a tracking feature with a few browsers.
Described in RFC 6797, HTTP Strict Transport Security (HSTS) is a mechanism that helps websites redirect users from the insecure HTTP version to the encrypted HTTPS version.
For example, if a user puts www.google.com into their browser, it's HSTS that sends them to https://www.google.com.
The issue is, someone thought it might be troublesome if the User Agent – that is, your browser – had to go through a redirect every time a user visited the https site.
So the authors of HSTS created a mechanism for browsers to remember the HSTS policy of sites they've visited.
That's exactly what Sam Greenhalgh has identified as a kind of super-cookie. His point is that an HSTS pin is set for each HTTPS-redirected site you use, it's unique to user and site, and it's readable from your browser settings by any site.
“Once the number is stored in the system it could be read by other sites in the future. Reading the number just requires testing if requests for the same web addresses are redirected or not,” Greenhalgh writes.
Greenhalgh notes that some browsers allow the HSTS flags to be cleared, so that in Chrome, Firefox and Opera the problem is mitigated somewhat. By the way, Internet Explorer doesn't support HSTS.
But Safari is the real killer-- When using Safari on an Apple device there appears to be no method that HSTS flags can be cleared by the user. HSTS flags are even synced with the iCloud service so they will be restored if the device is wiped.
In this case the device can effectively be branded with an indelible tracking value that you have no way of removing.
It's something that needs a malicious site owner for an exploit. Greenhalgh also notes that the issue was described in 2012 by Mikhail Davidov, calling implementation by a site owner “nearly trivial”.
Overall, Google has told Greenhalgh that “defeating such fingerprinting is likely not practical without fundamental changes to how the Web works”, which seems odd since IE manages to navigate the Web without supporting HSTS at all.
It could be that Google feels some investment in HSTS, since its Adam Barth is one of RFC 6797's three authors.
Get a powerful Linux Dual-Core dedicated server for less than $2.67 a day!