Live data from Hacker News

Ask HN: Maybe found huge security problem, unsure what to do

news.ycombinator.com

1–10 of 52 posts

Ask HN: Maybe found huge security problem, unsure what to do

#1
Let me just start off saying I'm 100% amateur and I don't really know that much so I could be all wrong.

I was browsing the website and got redirected to a random URL. Tracing the requests back I found that the redirect was caused by improperly sanitized html. The exploit more or less gives you an iframe worth of functionality. This allows for very sophisticated phishing.

Firefox is not vulnerable to this (You might be able to guess what the vuln is from that).

Now this actually pales in comparison to the 2nd exploit I found. I'm significantly less sure this works but I'm still pretty sure it will. I have only tested it out on the preview mode and not published.

The preview mode DOES sanitize(hits their server and comes back, basic stuff like gets cleaned up). It just doesn't do a very good job at it. Now, they could have 2 different checks, one being more secure when publishing but this seems unlikely. I'm not really familiar with the applicable laws so I'm not willing to actually publish an attack to test.

The 2nd exploit allows me pretty much free reign on their page. More or less it lets you execute whatever javascript you want.

I have sent the company 2x messages through a form they have for reporting securities vulnerabilities. However I'm not even sure that they got through as I never received a confirmation email (it said one would be sent).

I tried calling as well but I just discovered it last night and I haven't gotten through to anyone who knows anything.

My conundrum is this is an EXTREMELY popular website. Top 100 on Alexa, 30bn+ market cap. If this vulnerability is actually real I'm not sure I'm comfortable sitting on the information for a prolonged period of time considering how easy it would be to exploit.

In the meantime I'm going to continue to try and contact the company but I'm not really sure what my next steps should be otherwise.

Re: Ask HN: Maybe found huge security problem, unsure what to do

#3
Look in linkedin for people working in security for that company, and invite them to connect. In the connection message state directly the problem.

Do this with technical people, but also with it managers from the company and its worth sending it to the CEO.

Explain what are the risks (is it persistent xss visible by other users in a forum etc)

These things are only important until some manager says they are important, so try to explain the business and public image risk of the exploit to a high level manager via linkedin in non technical terms, ideally with a demo. If they forward the email to the it department i bet that then they would act.

Last case if responsible disclosure doesnt work after 3 /6 months: public disclosure via some news site. All of the sudden it gets fixed in two days, they end users end up being better off in the long term.

Unpatched exploits that stay there for years are the bread and butter of hackers, and the short term risk introduced by the public disclosure is compensated by the fact the users get protected in the end.

Re: Ask HN: Maybe found huge security problem, unsure what to do

#4
When it comes to vulnerability reporting and/or disclosure, there are two schools of thought; "responsible disclosure" and "full disclosure". Unfortunately, what "full disclosure" and "responsible disclosure" actually mean can vary a whole lot. For example, some define "full disclosure" as immediately publishing/disclosing the vulnerability and/or with working exploit code, but more level-headed folks define "full disclosure" as trying to contact the vendor and giving them at least 5 days to respond before publicly disclosing any information [1].

The safe and sane approach is to contact CERT [3,4] through their vulnerability reporting page [5] and let them contact the vendor. If you're curious, the CERT disclosure policy is good reading [6].

[1] http://www.wiretrip.net/p/libwhisker.html

[2] http://www.cert.org/vulnerability-analysis/vul-disclosure.cf...

[3] https://www.us-cert.gov

[4] https://www.cert.org

[5] http://www.kb.cert.org/vuls/html/report-a-vulnerability/

[6] https://www.cert.org/vulnerability-analysis/vul-disclosure.c...

Re: Ask HN: Maybe found huge security problem, unsure what to do

#7
At every IT company I ever worked or friends of me worked there were huge security holes. The common thinking of management is, though, that it's under control. Exposing these holes publicly results in getting fired or maybe even getting sued (because usually job contracts prohibit you from doing something that "harms" the company or its image). I don't think there is much that can be done about it. I certainly wouldn't risk my job, decrease the chance to get a job from other companies and knowing that for all that I could only free the world from one security bug, when million new ones are created daily.

Re: Ask HN: Maybe found huge security problem, unsure what to do

#8
post #2

This is laughable, you act like you have found a RCE in said company. It's just a XSS, not that serious dumbass. I will confirm your statement of being a 100% amateur.

What do you think this site is? Reddit?

Some of the circlejerks around certain topics here are very reddit-like, indeed.

Re: Ask HN: Maybe found huge security problem, unsure what to do

#9
post #7

At every IT company I ever worked or friends of me worked there were huge security holes. The common thinking of management is, though, that it's under control. Exposing these holes publicly results in getting fired or maybe even getting sued (because usually job contracts prohibit you from doing something that "harms" the company or its image). I don't think there is much that can be done about it. I certainly would…

To be clear I don't work for the company. I just happened across it while on their website. More or less I got suspiciously redirected from one of their listings and I started digging from there.

Re: Ask HN: Maybe found huge security problem, unsure what to do

#10
post #4

When it comes to vulnerability reporting and/or disclosure, there are two schools of thought; "responsible disclosure" and "full disclosure". Unfortunately, what "full disclosure" and "responsible disclosure" actually mean can vary a whole lot. For example, some define "full disclosure" as immediately publishing/disclosing the vulnerability and/or with working exploit code, but more level-headed folks define "full di…

Thank you so much for this. (xpto123 as well).

I tried calling but just got bounced around and I'm not sure anyone actually understood/cared. I've got a nice early season cold going so not really interested in sitting on the phone for hours so I've given up on that.

I'm going to email blast as many of the emails I can get and if I don't hear anything back from them by Monday I'll pass it onto CERT.

Post reply on HN