6 ms·
> They are almost never intentional. Somebody had to specifically code the application to concatenate into the string: > smoker=1&parent=&pregnant=1&mec=&zip=
by 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.
- shard972 12y ago> 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. Considering they spent 1.7 billion on the site, I simply cannot believe that they were so unorganised and lazy on their testing that they couldn't find this. Otherwise I don't know what to think anymore.
- GabrielF00 12y agoI don't think it's accurate to say "they spent 1.7 billion on the site". I think the $1.7 billion figure comes from this OIG report http://oig.hhs.gov/oei/reports/oei-03-14-00231.pdf http://oig.hhs.gov/oei/reports/oei-03-14-00231.pdf However, the OIG report has a number of important caveats: * The list of 60 contracts in the report includes contracts to support state websites and for programs unrelated to the website (for instance, I found an $85 million contract related to accountable care organizations, which doesn't seem to have any connection to the website). * The $1.7 billion is not the amount expended, it's the estimated value at the time the contract was awarded if all the options are exercised. When you look at the individual contracts, this estimated value turns out not to be very useful. Some contracts had double the estimated expenditure, some had $0 expended. Looking at the total amount expended, you get a figure of $500 million. So I think it's more reasonable to say that they spent $500 million on various projects to implement the law, including both the user-facing website and all the behind-the-scenes stuff.
- zaroth 12y agoGood digging, and I think you're right, this certainly explains how the data could have inadvertently made it from Referrer into the request.
- toothbrush 12y agoThere is also such a thing as criminal negligence, right?
- 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.