4 ms·
It's hard to offer advice without knowing more details, but I think it's good that you're not providing many details in a public forum like this. Some issues c
by cperciva 16y ago
It's hard to offer advice without knowing more details, but I think it's good that you're not providing many details in a public forum like this.
Some issues can be fixed quickly; others take a long time. The AWS signing bug I found, for example, took over 6 months to fix, because Amazon had to create a new signing scheme and then update a lot of code to use it. Because of this, I would hesitate to specify a hard expiry date; my usual approach is to ask for periodic status reports and only "turn up the heat" if it sounds like the issue isn't being taken seriously.
If they don't seem to be taking the issue seriously, there's two possibilities: 1. They're not taking the issue seriously; 2. They didn't take you seriously and never actually looked at the issue. In either case, it might be useful to work through someone who has experience in vulnerability handling; myself and tptacek come to mind as people who could help here.
- jacksoncarter 16y agoIt is a very difficult problem to solve. I do know that. It's been about 9 months since I first informed them of the issue. I sent them source code that illustrates an attack. Many of their customers are being affected right now, by something. I can't prove that this is the mechanism behind the current wave of attacks, though I can prove that this mechanism would allow a hacker to compromise sites exactly as is being described by victims. They did take me seriously. I believe they aren't fixing the problem because they will have to rewrite a lot of their code, their customers will have to rewrite code, and many will be forced to find another provider all together, which means the solution has negative financial impacts. Not solving it means negative financial impacts on their customers in lost time to rebuild affected data. It's very well possible that malicious people know about this and are using it right now to gather usernames and passwords for later attacks. Hundreds, perhaps thousands, of databases may have been siphoned off already. How do you "turn up the heat" ?
- cperciva 16y agoHow do you "turn up the heat" ? Start saying things like "if you don't start making progress on this, I'm going to publish details". Contact Mitre and ask for a CVE #. Write to CERT, CERT-FI, or NISCC and ask them to help you. Write a blog post about the issue and send it to them saying "I'm going to put this online on Monday unless I hear from you first". Then put the blog post online on Wednesday. EDIT: Also, try different communications channels. Sometimes a phone call is far more effective than an email.