6 ms·
This is pretty shocking. What is PII doing in the query string in the first place? Disclosing pregnancy status from an insurance application sounds like a possi
by zaroth 12y ago
This is pretty shocking. What is PII doing in the query string in the first place? Disclosing pregnancy status from an insurance application sounds like a possible HIPPA violation and runs afoul of various state laws around 'Insurance Information and Privacy Protection'. E.g http://www.leginfo.ca.gov/cgi-bin/displaycode?section=ins&group=00001-01000&file=791-791.29 http://www.leginfo.ca.gov/cgi-bin/displaycode?section=ins&gr.... See Section 791.13(k). That's just CA law but many states followed with their own version. (IANAL)
I think the really big penalties come into play when medical information is 'personally identifiable'. Since this data is going to Google, Facebook, and Twitter (really?!) with 3rd party cookies, or even without, it would be hard to argue this data is not personally identifiable.
It's not like they didn't know they weren't sending this data out. Or perhaps the highly advanced debugging prowess of "Chrome Inspector" is beyond their pay grade.
Edit: Oh it's not even just Referral leak it's actually it the request in some cases, so blatantly intentional. :-(
- threeseed 12y ago> Oh it's not even just Referral leak it's actually it the request in some cases, so blatantly intentional. Be careful about throwing the term intentional around. There is nothing to suggest this is the case. It's just a shocking breakdown in security/testing processes and/or a bug. We see security/privacy issues everyday. They are almost never intentional.
- Alupis 12y ago> They are almost never intentional. Somebody had to specifically code the application to concatenate into the string: > smoker=1&parent=&pregnant=1&mec=&zip=85601&state=AZ&income=35000
- darkerside 12y agoIt could have been passed along as a returnUrl. Never attribute to malice what can be explained by incompetence.
- acdha 12y agoReading the example more closely, that's part of a URL: https://4037109.fls.doubleclick.net/activityi;src=4037109;type=20142003;cat=201420;ord=7917385912018;~oref=https://www.healthcare.gov/see-plans/85601/results/?county=04019&age=40&smoker=1&parent=&pregnant=1&mec=&zip=85601&state=AZ&income=35000&step=4 https://4037109.fls.doubleclick.net/activityi;src=4037109;ty...? Unfortunately, a quick Google search doesn't explain what the oref parameter does but from the name I'm assuming it's something like "original referrer". You don't need malice to explain this – it's entirely plausible to imagine that some people wanted to track user activities and they had a staggering lapse in HIPAA auditing due to the rush of getting the site out and stabilized.
- declan 12y ago> rush of getting the site out and stabilized. I agree that there's no evidence, at least not yet, of malicious intent. But remember that the "rush of getting the site out" took place back in 2012-2013, with a launch in 2013. It's 2015 now.
- acdha 12y agoOh, sure – I just suspect that project has been in death-march mode for the last few years. I'd be shocked if the initial launch & stability rush wasn't immediately followed by “now that that's done, we have this backlog of postponed requirements…”
- Alupis 12y agoWould it excuse it if it were, say, not HealthCare.gov but rather some private company's website? (probably not)
- acdha 12y agoI don't see anyone excusing it – only discounting the supposition that it was intentional. The only reason this is particularly newsworthy is that it's a .gov service connected to a contentious political issue – I mean, my health insurance company uses the same DoubleClick tracking service and I doubt I could even get a reporter to call me back if I tried to peddle some conspiracy theory about it.
- scintill76 12y agoHere's the full URL, which was embedded into another URL: https://www.healthcare.gov/see-plans/85601/results/?county=04019&age=40&smoker=1&parent=&pregnant=1&mec=&zip=85601&state=AZ&income=35000&step=4 Looks like a plausible search URL from a <form> element with GET. Putting it into the querystring instead of a POST body is a bit surprising, but I think not utterly negligent. Then some Javascript code (maybe not even healthcare.gov's in-house code) looked at window.location.href and put it into another URL, and nobody noticed or stopped it. That is negligent, but more understandable, and fair to presume as unintentional, I think. There's plenty to be legitimately upset about here, but your comment ("specifically code the application to concatenate") seems to imply the code has something outrageous like "&pregant="+currentUser.pregnant+"&smoker="+currentUser.smoker somewhere, without you giving any evidence that's the case.
- deleted 12y ago[deleted]
- Turing_Machine 12y ago"Putting it into the querystring instead of a POST body is a bit surprising, but I think not utterly negligent." Putting sensitive data into query strings has been considered bad practice for a very long time. To name just one problem among many, it goes into the browser history.
- scintill76 12y agoYes, it's hard to argue against that. I didn't focus on it because the privacy harm of leaking to third parties seems greater than that caused by the URL going into browser history or server logfiles (the most relevant concerns I see.) This doesn't excuse them, but it's interesting to consider that probably tens of thousands of sensitive Google, etc. searches per day go into query strings. I guess the difference is that Google doesn't know if your freeform search is sensitive, whereas a "Pregnant?" checkbox is known to be sensitive. But maybe general search engines should not be using query strings either, just in case.
- 12y ago
- brandonb 12y agoNot intentional. This was a bug.
- zaroth 12y agoExcept when it is: Medicare spokesman Aaron Albright said outside vendors "are prohibited from using information from these tools on HealthCare.gov for their companies' purposes." The government uses them to measure the performance of HealthCare.gov so consumers get "a simpler, more streamlined and intuitive experience," he added. http://apnews.myway.com/article/20150120/us--health_overhaul-privacy-8b7c5d925b.html http://apnews.myway.com/article/20150120/us--health_overhaul...