Slashdot Mirror


How Do You Handle the Discovery of a Web Site Disclosing Private Data?

An anonymous reader writes I recently discovered that a partner web site of a financial institution I do business with makes it trivially easy to view documents that do not belong to me. As in, change the document ID in a URL and view someone else's financial documents. This requires no authentication, only a document URL. (Think along the lines of an online rebate center where you upload documents including credit card statements.) I immediately called customer service and spoke with a perplexed agent who unsurprisingly didn't know what to do with my call. I asked to speak with a supervisor who took good notes and promised a follow-up internally. I asked for a return call but have not yet heard back. In the meantime, I still have private financial information I consider to be publicly available. I'm trying to be responsible and patient in my handling of this, but I am second guessing how to move forward if not quickly resolved. So, Slashdot, how would you handle this situation?

137 of 230 comments (clear)

  1. Krebs by kylemonger · · Score: 5, Insightful

    Give the information to Brian Krebs and have HIM call them. I guarantee you they will get off their asses and do something then.

    1. Re:Krebs by MrBigInThePants · · Score: 3, Funny

      Absolutely. Tell lots of high profile people who loose lips. Hey, tell your favorite prostitute while you are at it!

      Blab about it on the internet on a very popular website also. That will increase your chances of being personally identified before you notify the appropriate people and ensure that the preemptive action they will take against you will not work. Alternatively they can also use that against you after the fact instead/as well.

      I would also suggest as "icing on the cake" to paint red circles of decreasing size around you anus to make targeting easier.

      Alternatively you could ignore the truly SHITTY advice here on slashdot and be discrete and anonymous.

    2. Re: Krebs by bill_mcgonigle · · Score: 2

      I like Krebs, so DO NOT put him in a position where he has to think about protecting your identity. For the love of all that is holy, boot Tails on a junker laptop at a cafe you never go to and use a throw-away mail account or pastebin it and leave a comment.

      Or just walk away. You have no duty to put your life on the line here - everybody who supports the system that will throw you to the lions for being a good guy will suffer for it in kind. You're not obligated to be their saviour. Sucks, but play the shitty hand you're dealt - don't bet all your money wishing you didn't just have a pair of threes.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    3. Re:Krebs by Jane+Q.+Public · · Score: 4, Interesting

      Give the information to Brian Krebs and have HIM call them. I guarantee you they will get off their asses and do something then.

      Don't be so sure.

      I had a similar problem with a bank back in 2000-2001. I called their customer service dept. and they put me in contact with the IT dept. I explained that their web banking portal was spewing private information all over the place. (I was quite alarmed, since I had noticed this when doing my own online banking.) They said they'd see to it right away.

      A couple of weeks go by, it's still the same. Now, mind you, this was a MAJOR leak to anybody who knew about it. Arguably worse than OP's problem. So I called them again. I was assured that they were right on top of it.

      After about another month went by, I went into the main branch of the bank, and SHOWED this to one of the managers. He seemed quite concerned. Another couple of months go by... nothing.

      I finally called them up and said if they didn't fix the problem, I was going to the newspapers with it. It didn't faze them. I actually did take it to the local paper, and they weren't interested in the story. (Turned out later, they were best buds with this particular bank.)

      Anyway, long story short: they did nothing. It took them a full year and a half to fix the problem. If I had been an unethical person, I could have emptied out the accounts of MANY people over that time.

    4. Re:Krebs by camperdave · · Score: 5, Interesting

      Banks are regulated (at least, they are around here), so take it to the regulatory commission if the bank themselves don't do anything. Also, for most companies, unless it is in writing, it didn't happen. Don't call. Snail-mail.

      --
      When our name is on the back of your car, we're behind you all the way!
    5. Re:Krebs by pepty · · Score: 5, Informative

      Call the bank and ask for their "agent of service", This is the first step you take when you sue a corporation: find out the lawyer you need to send the paperwork to. Not that you will actually be suing them, but if anyone can light a fire under the bank's IT staff it's their lawyer.

    6. Re:Krebs by plover · · Score: 3, Insightful

      Nobody took computer security seriously back in 2001. Things have changed a lot since then. For example, if you were to contact that same bank with the same information today, they would likely know better and would now contact the FBI and have you arrested on charges of violating the Computer Fraud and Abuse Act.

      Actually, contacting the FBI might not be a bad choice for the story submitter. They would probably be very interested in working with that bank to shut this problem down quickly.

      --
      John
    7. Re:Krebs by Anonymous Coward · · Score: 1

      Seriously? You went through all of this and did not immediately close your account?

    8. Re:Krebs by Anonymous Coward · · Score: 4, Informative


      I finally called them up and said if they didn't fix the problem, I was going to the newspapers with it. It didn't faze them. I actually did take it to the local paper, and they weren't interested in the story.

      Notorious troll Weev" did the above (although he went to the media FIRST apparently) and included the exposed data, and as a result was sentenced to 41 months in federal prison and $73,000 in restitution. The EFF and many others condemned the prosecution.

    9. Re:Krebs by ArcadeMan · · Score: 4, Funny

      I agree. A friendly game of baseball is the perfect opportunity to discuss security issues with them.

    10. Re:Krebs by Jane+Q.+Public · · Score: 1

      Banks are regulated (at least, they are around here), so take it to the regulatory commission if the bank themselves don't do anything. Also, for most companies, unless it is in writing, it didn't happen. Don't call. Snail-mail.

      I probably should have done this. I didn't WANT to create a stink, but by the end of this sequence of events I was just plain dumbfounded that they would be -- pardon my language -- so fucking stupid.

      When going to the paper didn't work, I probably should have contacted the authorities. Instead, I just switched to another bank.

    11. Re:Krebs by Anonymous Coward · · Score: 1

      you left out the part where you called brian krebs.

    12. Re:Krebs by Jane+Q.+Public · · Score: 1

      Notorious troll Weev" did the above (although he went to the media FIRST apparently) and included the exposed data, and as a result was sentenced to 41 months in federal prison and $73,000 in restitution. The EFF and many others condemned the prosecution.

      Very different situation. This leak was TO computers, and didn't involve going to "unauthorized" addresses. The information was right there on your local machine if you knew where to look. No remote exploration necessary. I would rather not discuss the details but if you knew them I am sure you would agree that it was alarmingly stupid.

      Agreed, though, that Weev was railroaded. He did nothing wrong except to piss off powerful people. It was (is) a travesty of justice. Same with Aaron Swartz.

    13. Re:Krebs by Jane+Q.+Public · · Score: 1

      Nobody took computer security seriously back in 2001. Things have changed a lot since then.

      I have to agree with you in general, but banks should have been concerned about it. Online banking was a fairly new thing, but even then, I am pretty sure this mistake violated Federal regulations.

    14. Re:Krebs by Anonymous Coward · · Score: 1

      Notorious troll Weev" [wikipedia.org] did the above (although he went to the media FIRST apparently) and included the exposed data

      Note quite true, he first downloaded what? 114,000 customer records before contacting someone on that list about the vulnerability? He reported it AFTER exploring it en mass, and while his motives *may* have been pure... the degree he went to can and were used to harm him.

      I'm currently sitting on a statewide vulnerability which I *could* use to exploit an order of magnitude more users... but have refrained from doing so while I seek legal advice as to how to best approach the state in question over this issue as I do not think simply emailing them about a system they think is foolproof would be enough.

    15. Re:Krebs by penguinoid · · Score: 1

      Or in this case, get a computer not traceable to you to download (but not store) every single document they have, on a loop forever. Whoever checks the server logs will freak out and it will get fixed. And if it is traceable to you, you'll get fixed too (but rather too late for that since you already brought yourself to their attention, and because of you they have to spend money and they're not happy).

      --
      Don't waste your vote! Vote for whoever you want, unless you live in a swing state it won't matter anyways
    16. Re:Krebs by MrBigInThePants · · Score: 1

      Having sex with a spy is on my bucket list.

      Although knowing my luck it will be a forced anal invasion in Guantanamo...but beggars can't be choosers I guess...

    17. Re:Krebs by Jane+Q.+Public · · Score: 1

      Correction: it wasn't a "mistake". It was intentional. It was just half-assed design.

    18. Re: Krebs by devilspgd · · Score: 3, Insightful

      Or just walk away.

      While true, this solution doesn't allow one to protect their own data which is also exposed.

      --
      Give a man a fish, he'll eat for a day, but teach a man to phish...
    19. Re:Krebs by camperdave · · Score: 2

      Having sex with a spy is on my bucket list.

      "Never mind why. Just clip this lapel mic to your blouse."

      --
      When our name is on the back of your car, we're behind you all the way!
    20. Re:Krebs by drolli · · Score: 2

      As a user you are not supposed to make sensible input to the support hotline. Also the head of the local branch is a user.

      IT departments in banks are behemoths, never changing course. They can't react quickly. A mess of different never integrated systems which were kept over decades, "tailored" solutions by consultants with too little a time budget in the projects, and department heads for whom the internet is a new technology create an impenetratable mess where even the support doen not know whom to turn to.

    21. Re:Krebs by davester666 · · Score: 1

      Or forward all the information to Jeb Bush. He'll know what to do!

      --
      Sleep your way to a whiter smile...date a dentist!
    22. Re:Krebs by Anonymous Coward · · Score: 3, Informative

      Do NOT give them anything in writing that is an admission of "hacking".

    23. Re:Krebs by khoonirobo · · Score: 1

      Err, I think you meant 'discreet', not 'discrete'.

    24. Re:Krebs by AchilleTalon · · Score: 3, Interesting

      Having written the on-line banking communication protocol of a bank back in 1995 I can assure you they were not taking security seriously. I explicitly asked about requirements for encryption and they had none. They didn't want to bother with encryption because the infrastructure was running on dialup lines connected directly to their infrastructure and they wanted to be the first bank to make on-line banking available to its customers. At this time, the internet was in its infancy, hence the choice for the dialup infrastructure, and everyone was subscribing dialup lines for the Internet access DSL and cable-modem was still waiting to be invented. It was even Windows 3 and OS/2.

      --
      Achille Talon
      Hop!
    25. Re:Krebs by PetiePooo · · Score: 2

      ...but buggars can't be choosers I guess...

      Fixed that for ya...

    26. Re:Krebs by Anonymous Coward · · Score: 1

      Work for/on Microsoft support too. Read them the warrenty "card" with the software (VB3 at the time), that said it start at the first phone call and lasted 90 days. I was told that it was not under warrenty. Asked who sent me writen notatifaction of change of warrenty. Their lawyer called support and told the to help me. It took a week for them to get ready (build machine and reload from old tapes) they were able to get find and fix my issue.

      Lawyers are at best support reps ever!

    27. Re: Krebs by BVis · · Score: 2

      I guarantee you that their lawyers can beat up his lawyers. If he sues, he'll get buried in paper, causing legal fees to quickly attain unmanageable levels, then they'll counter-sue for defaming their name. He'll be lucky to walk away with the shirt on his back.

      America!

      --
      Never underestimate the power of stupid people in large groups.
    28. Re:Krebs by cellocgw · · Score: 1

      Having sex with a spy is on my bucket list.

      Although knowing my luck it will be a forced anal invasion in Guantanamo...but buggers can't be choosers I guess...

      FTFY

      --
      https://app.box.com/WitthoftResume Code: https://github.com/cellocgw
    29. Re:Krebs by datavirtue · · Score: 1

      Does it violate their terms of service? Dig up the terms of service and if they say that they will protect your information then it is a violation...numerous lawyers will help you for free.

      --
      I object to power without constructive purpose. --Spock
    30. Re:Krebs by cusco · · Score: 1

      Wow, hard to believe that this still happens. First encountered this when I opened my first (and only) online banking account at SeaFirst bank in the late '90s. When I realized that in order to get into someone else's account all I had to do was change the account number in the URL I took some screen shots and sent it off to their webmaster. It was told that it was fixed within a couple of weeks, but I was so appalled that it was even possible that I had them delete my online profile and lock my account from changes made from an online account. Have never signed up for online banking since because every few years there's another of these stories appearing, I think the most recent was Chase just two years ago.

      This is the inevitable result of outsourcing all your IT work to the lowest bidder.

      --
      "Think about how stupid the average person is. Now, realise that half of them are dumber than that." - George Carlin
    31. Re:Krebs by MrBigInThePants · · Score: 1

      I actually meant concrete. Possibly excrete.

      But thanks for being discreet.

    32. Re: Krebs by MrBigInThePants · · Score: 1

      Yeah yeah yeah.

    33. Re:Krebs by MrBigInThePants · · Score: 1

      Actually that came up in the spell checker when I mistyped it and I was tempted.

      Of course it ruins the metaphor since I am the buggaree, not the buggerer.

    34. Re:Krebs by cusco · · Score: 3, Interesting

      In the last '90s I worked as System Operator for a company which sent several thousand automated account renewals to credit card companies each month. We had been sending 9-track tapes via Fed Ex, and I was tasked with converting all these to digital transfers. We ended up with a mish-mash of different methods, dialup modem, encrypted email attachments, etc. but American Express had a rather unique approach.

      They had us FTP an unencrypted, unzipped text file to a folder with our account number on their ftp site. Logged in as anonymous. With full access to all the other folders showing all their other customers' data transfers. They didn't clean up the folders either, so some of the other customers had a year's-worth of data transfers piled up. We couldn't believe it.

      --
      "Think about how stupid the average person is. Now, realise that half of them are dumber than that." - George Carlin
    35. Re:Krebs by Wootery · · Score: 1

      This is the inevitable result of outsourcing all your IT work to the lowest bidder.

      And of having no real liability.

    36. Re:Krebs by vakuona · · Score: 2

      I think you will find that banks have real liability when they fail to protect customer data. At least here in Europe they would.

    37. Re:Krebs by Jane+Q.+Public · · Score: 1

      I explicitly asked about requirements for encryption and they had none.

      I have intentionally chosen not to reveal what the actual problem was. But believe me, it was worse than just lacking encryption.

    38. Re:Krebs by Jane+Q.+Public · · Score: 1

      It wasn't like that. THEY were spilling information. I wasn't going looking for it.

    39. Re:Krebs by Jane+Q.+Public · · Score: 2

      He reported it AFTER exploring it en mass, and while his motives *may* have been pure... the degree he went to can and were used to harm him.

      Contrary to what was reported from many sources, he DID go to them first, before publishing the exploit. The fault for not fixing it immediately rests on them, not him.

      What he did was normal curiosity. Hell, I've done it. In fact I don't know of any web or security professionals who haven't. Got an ID in the URL? Increment it by one, see what happens. We all do it.

      Granted, we don't normally explore it to the degree he did. But what he did was ridiculously simple, and hardly even deserves the term "hacking" at all. What THEY did was akin to leaving the back gate open and putting out a sign that says "Come on in!", then complaining about it when someone did.

      Anyway, I'll repeat what I said about my own experience: I didn't need to go "fishing" for information in that case. It was being sent TO ME, just in a non-obvious way. I stumbled across it, I didn't go looking for it or trying to exploit it. I sure could have, though.

    40. Re: Krebs by devilspgd · · Score: 1

      I doubt terminating his account would remove any existing data, although it may well reduce the amount of additional data that gets exposed going forward. It doesn't solve the problem.

      --
      Give a man a fish, he'll eat for a day, but teach a man to phish...
    41. Re:Krebs by SmaryJerry · · Score: 1

      Whenever you call them tell them you are recording the conversation for quality assurance purposes.

    42. Re:Krebs by Anonymous Coward · · Score: 1

      Very true.

      When I worked for HP (when it still sold test instruments), a buddy of mine who was responsible for telecom/datacom analyzers called on Wells Fargo headquarters in San Francisco. They brought the HP T1/T3 analyzer plus a datacomm analyzer for a pre-sales demo. Basically the former let's you examine all the T1/T3 channels "in the raw". With T1/T3 you can keep each channel separate as a voice or data channel or you can bond them together as a combined data channel. It's complicated enough that having this equipment can simplify the management of their use. In addition, you could pop off a particular channel and feed it into an RS232 connect on the instrument and then pipe that into a datacomm analyzer to read out the raw data and decode it on-the-fly if it's implementing some data protocol like X.25 or PPP. That was the "sale value proposition".

      So anyway during the demo the entire corporate IT group was gathered around and my buddy was running through the paces of the demo. He switched the T3 channel and out popped text data on the datacomm analyzer screen. One guy recognized the phone line and text preamble as an ATM modem line. Almost immediately name, account and PIN rolled by. The manager picked up on this a few seconds after everyone else and immediate lost his top and ended the demo. His last words were something to the effect of: "I don't want your damn company or equipment in this building ever again!!" The sales rep tried to smooth things over and recover the situation but apparently never was able to.

      The net of this story:

      Wells Fargo didn't encrypt any connections or traffic from any remote ATMs

      Wells Fargo basically relied on nothing more than "security through obscurity" as an IT strategy

      Wells Fargo's ATMs were trivially vulnerable to "replay attacks" at the very least, with or without "social engineering"

      Wells Fargo probably hasn't changed any of its security to this day

      Wells Fargo is now the biggest bank in the US

      I immediately closed my WF account after hearing this and I'm still leery about doing business with them. I could tell you another story about WF mortgages that would raise the hairs on the back of your neck as well but that's another story about the systemic fail of CDS/CDO/derivatives for another day.

  2. Notify CTO, CFO & CEO offices by BoRegardless · · Score: 4, Funny

    Those people will definitely take your info and get it acted upon.

    1. Re:Notify CTO, CFO & CEO offices by Mycroft-X · · Score: 1

      This -- in a small organization the CEO reads their email and forwards to the appropriate people. In a large organization the CEO has a team of people that help them with this. Either way, it is likely to get top down (rather than bubble up) attention.

    2. Re:Notify CTO, CFO & CEO offices by whoever57 · · Score: 1

      In my experience, it won't.

      I reported to a small non-profit that their list of email addresses had leaked. I knew this because I used a unique address when registering with the site and I later started getting SPAM at that address. It might not have been a hack that caused my address to leak, but, irrespective of the means by which my email address had leaked, there should have been an investigation.

      I reported it to the CEO, who passed it to the IT head, who basically could not get his head around the idea that there might be a problem.

      --
      The real "Libtards" are the Libertarians!
    3. Re:Notify CTO, CFO & CEO offices by AK+Marc · · Score: 4, Interesting

      I worked for a 10,000+ person company, the CEO read the emails identified by his secretary as important. I worked for a 200+ person tech company where the CTO read some of the emails the secretary printed out for him. He didn't have a computer (not in the office, and not at home). If he sent an email, he dictated it to his secretary, and she would then send it for him.

      For a 5-man company, you may find CEOs read their own emails. For larger than that, the CEOs don't read emails. The few I know that did, used their personal email for business, and the business email was essentially forwarded to the info@ email box.

      I've found that snail mail got insanely quick response. It would get to the CEO and be read. Only obvious advertisements would be withheld by helpers, and even then not aggressively so.

    4. Re:Notify CTO, CFO & CEO offices by Harlequin80 · · Score: 1

      The best approach is to call them. However most people don't feel comfortable doing this.

      If you pick up the phone and call their head offices number (as opposed to customer support number) and ask for the CEO you will almost always get put through to them. You may hit a voicemail system after that but because most people won't actually call someone they voicemails are usually listened to. Keep it polite, and to the point and you will be surprised as to how quickly they will act.

    5. Re:Notify CTO, CFO & CEO offices by AK+Marc · · Score: 1

      The 10,000 person company I worked for, that would never work. At best, you'd get his secretary, who would hand-write a note. Though, the smaller companies I've worked for, that'd work if you asked for him by name. But "may I speak with the CEO" coming in to the reception would get you hung up on in many cases. If you don't know enough to know who the CEO is, then you obviously can't actually need to speak with him. Though hanging up on people is rude, so death-by-hold was second on the list. Put them on hold. Leave them there until they hang up. Problem solved, and you never had to tell them "no".

    6. Re:Notify CTO, CFO & CEO offices by pepty · · Score: 3, Insightful

      In my experience, it won't.

      I reported to a small non-profit that their list of email addresses had leaked. I knew this because I used a unique address when registering with the site and I later started getting SPAM at that address.

      Most likely, the non-profit sold your email address (along with the rest of their list), leading to embarrassment all around when you contacted them about the spam.

    7. Re:Notify CTO, CFO & CEO offices by Alan+Shutko · · Score: 4, Informative

      In my Fortune 25 company, we have a department of people devoted to resolving issues of people who contact the CEO, President, or other members of senior staff. This method absolutely will light a fire under the IT staff to fix it. I don't know whether he reads every incoming letter or email, but I do know that each one is handled by the presidential escalation team, and tracked, and reported out regularly.

      We also have a Chief Information Security Officer who will personally latch onto this like a bulldog and ensure that it's fixed. We had a breach a number of years ago and it's still used as a reminder that "That will NOT happen again."

    8. Re:Notify CTO, CFO & CEO offices by Harlequin80 · · Score: 2

      I call the CEOs, State Managers, Divisional Directors etc etc of companies that range in size from 20 person to 75,000 person on a daily basis for my job. You absolutely need the name in order to get anywhere but that information is very very simple to get. To get through to those people all you need to do is sound like you expect to be put through.

      Worst case scenario is you are referred down the chain of command. There is no way that the CEO of a 10,000+ person is going to be the right person to speak to, however a conversation with their Head of IT that starts with John Doe said I should speak with you to sort this gets balls moving very quickly.

    9. Re:Notify CTO, CFO & CEO offices by Antique+Geekmeister · · Score: 1

      The "lighting a fire under the IT staff" too often results in the manager of IT having meetings, submitting checklists and expense reports, and doing _nothing_ to address the actual issue. Too often it's not a specific line of code, which can be corrected, but poor practices and attitudes about what security can and should be applied to projects.

    10. Re:Notify CTO, CFO & CEO offices by Big+Hairy+Ian · · Score: 1

      Nah! Show a reporter how to do it he'll then use it to spy on Celebs, Missing persons and murder victims just like they do with Voice Mail!

      --

      Build a Man a Fire, and He'll Be Warm for a Day. Set a Man on Fire, and He'll Be Warm for the Rest of His Life.

    11. Re:Notify CTO, CFO & CEO offices by coats · · Score: 1

      I've found that snail mail got insanely quick response...

      Especially if sent certified, return receipt requested. I've found that always has put things into the "Urgent!" bin on the receiving end.

      --
      "My opinions are my own, and I've got *lots* of them!"
    12. Re:Notify CTO, CFO & CEO offices by 0xG · · Score: 2

      This should not have been modded "Funny"; it's actually a very good strategy. I got taken off a corporate spam list (HP) by contacting "Office of the President". Nothing else I tried would work. Got a similar result with my ban when I couldn't get the payout amount for my mortgage. It was a reasonable request, but I was stonewalled - so I contacted the Pres. Got called back the same day with all the info I needed.

      --
      A pox on web designers who feel that window.innerWidth == screen.availWidth
  3. Post the URL here... by Anonymous Coward · · Score: 5, Funny

    ... That way we can help, too.

    Also, and this is a bit off topic, but what high school did you go to and what's your mother's maiden name?

    1. Re:Post the URL here... by mallyn · · Score: 3, Funny

      My mother's maiden name is Judy Garland and my high school is The Emerald City High School.

      --
      Most Respectfully Yours Mark Allyn Bellingham, Washington
  4. Buy some suntain lotion by Vinegar+Joe · · Score: 5, Funny

    You've hacked a bank and now you're a terrorist. Expect a visit from the FBI and a taxpayer funded trip to Cuba.

    --
    "The average reporter we talk to is 27 years old......They literally know nothing." - Ben Rhodes
    1. Re:Buy some suntain lotion by Bite+The+Pillow · · Score: 1

      Also, die in a fire. It would be more pleasant.

      Expect none of the above, but do take every possession you can out of the institution. Digital or otherwise.

      The art of the CEO mailbomb is lost, perhaps - send an email to the executives of every person attached to the company, and explain why you took action.

      NOT WHY YOU ARE CONCERNED.

      Why you took action is more meaningful. Take action first to protect yourself. If you want to file a lawsuit, it's going to be time consuming and expensive. Protect yourself first.

    2. Re:Buy some suntain lotion by pollarda · · Score: 4, Insightful

      Actually, this isn't too far from the truth. I've heard of a few cases where simply changing the URL has brought up documents that should be private and the person who reported it was brought up on charges for "hacking". Unfortunately, the public does not understand the difference between simply poking around and trying to mess up someone's system for nefarious reasons. Perhaps someone here on /. will remember the particular cases involved but as sad as it sounds, you are on a shaky legal foundation.

    3. Re:Buy some suntain lotion by An0nymous+Coward · · Score: 1

      We have a winner! If you discover security flaws, no matter how trivial, you are a criminal and a hacker. The only sane thing to do is cover up all evidence and tell no one.

    4. Re:Buy some suntain lotion by borcharc · · Score: 4, Insightful

      This shouldn't be modded funny, its the most likely outcome. You really should start thinking of protecting yourself now that you have made yourself a target.

    5. Re:Buy some suntain lotion by jmd · · Score: 1

      Yea.. one call to Tor Ekeland is a good start

    6. Re:Buy some suntain lotion by bloodhawk · · Score: 1, Insightful

      reporting vulnerabilities doesn't get you put in Jail, however manipulating sites without permission to look for them does. incidently the guy you linked did a lot more than "just" tell then just discover and tell them of a vulnerability, he exploited it and extracted a ton of information from their systems.

    7. Re:Buy some suntain lotion by bloodhawk · · Score: 1

      > reporting vulnerabilities doesn't get you put in Jail, however manipulating sites without permission to look for them does

      How orwellian of you. It is totally OK to report vulnerabilities but finding out about them, that's verboten.
      So when Target and Home Depot tell you that they've never had a report of a problem, you know that means their sites are 100% secure.

      of course it doesn't mean they are secure. That doesn't make it ok to try and break their security. Try going to the backdoor of banks and looking for a way to jimmy the door open to see if you can steal money, it won't matter whether you give the money you take back if you find a way in, or even if you didn't take any money, you will go to jail. If you want to help them do vulnerability scanning for free then approach them with your offering, if you can show you have the skills and background most will take a free offering of your labour, if not you can always out them as not even being willing to have their security checked.

    8. Re:Buy some suntain lotion by Anonymous Coward · · Score: 1

      I've heard of a few cases where simply changing the URL has brought up documents that should be private and the person who reported it was brought up on charges for "hacking".

      I worked for a company in the financial industry where this exact type of breach was discovered by our internal pen-testing team. The discovery of this flaw brought calls for swift action from C-level executives all the way up the chain. And it was resolved in a matter of about 2 weeks (with the affected functionality being taken offline for the duration of the fix.) At the same time, our security teams were directed to review access logs and other evidence to see if there was any possibility that somebody had already discovered the vulnerability and exploited it somehow.

      If some helpful looky-loo had discovered this vulnerability instead, and reported it, you can be damn sure that second piece would have been triggered as well - and yes, if it appears they exploited it to the tune of accessing 10's of thousands of people's info, they would have absolutely been a target for legal action.

      There's "I typed the link in wrong and got somebody else's information, this seems weird to me," and "I entered the link wrong, so then I confirmed the bug by entering 50,000 permutations of the wrong link to access a lot of other information, this is a pretty cool way for me to impress the media with my hacking savvy."

    9. Re:Buy some suntain lotion by cyberchondriac · · Score: 1

      Obama doesn't have anyone sent to Gitmo anymore.. expect a drone to bomb his house instead.

      --

      Look back up at my post, now look back down, you're on the Internet. Now look back up. I'm a signature.
    10. Re:Buy some suntain lotion by pbhj · · Score: 2

      >reporting vulnerabilities doesn't get you put in Jail, however manipulating sites without permission to look for them does. //

      Except that in this case the report is evidence of having "manipulated" the site "without permission" *.

      * web accessible documents have an assumed permission IMO; the removal of permission is performed by making the page only accessible with a password or similar auth.

    11. Re:Buy some suntain lotion by Lesrahpem · · Score: 2

      Actually, this isn't too far from the truth. I've heard of a few cases where simply changing the URL has brought up documents that should be private and the person who reported it was brought up on charges for "hacking". Unfortunately, the public does not understand the difference between simply poking around and trying to mess up someone's system for nefarious reasons. Perhaps someone here on /. will remember the particular cases involved but as sad as it sounds, you are on a shaky legal foundation.

      I thought of one particular case as soon as I read the summary: https://www.eff.org/cases/us-v....
      Aernheimer was charged under the CFAA for exposing a similar problem with AT&T's website.

  5. Good luck with that by Anonymous Coward · · Score: 1

    That's the same kind of flub that led, eventually, to weev getting caught.

    Now, mind you, weev is a troll, an asshole, and tried to profit off it, so you might be able to get away without CFAA charges if you avoid being a nazi troll and trying to extort 'em for money...but technically, you're already up for "circumventing" a "security control" so you may want to get a lawyer involved - and have your lawyer handle the negotiations with the institution.

  6. If you're in the United States, get a lawyer by Anonymous Coward · · Score: 5, Informative

    You called the bank and admitted manipulating the site in order to view other people's private financial information.

    Regardless of your intentions, you may be treated as the wrongdoer here. A security vulnerability exists, and unfortunately, you are the only one who has admitted to exploiting it. (It's entirely possible that the only person who has actually accessed someone else's private financial information is you.) Organizations in the United States have a long history of seeking sanctions (criminal or otherwise) against people like you who look for vulnerabilities in their systems (I think some similar cases were reported on Slashdot, and I know of one privately).

    Maybe withdraw all of your money out of your account in case they freeze it during their investigation (which means you wouldn't even have money to pay your lawyer), but beware that this could appear to be an indication of admission of guilt -- consult a lawyer first if there's time.

    1. Re:If you're in the United States, get a lawyer by nerdonamotorcycle · · Score: 2

      I agree. We all like to think we're being responsible citizens and good Samaritans by alerting people to dangerous situations. In an ideal world, that would be true. With the trend of treating whistleblowers in the U.S. as criminals, criminal prosecution is a very real possibility. Think about what happened to Randal Schwartz. I would absolutely not move forward with something like this without benefit of legal counsel.

    2. Re:If you're in the United States, get a lawyer by monkeyzoo · · Score: 1

      Goodness gracious. I hope this isn't the true state of the CFAA here in the US?!!

    3. Re:If you're in the United States, get a lawyer by Anonymous Coward · · Score: 2, Informative

      About 20 years ago I had something similar happen, I emailed people about a bug (not even as important as people's financial data, but still similar). It was a large company (30B market cap). Anyways, I received no response and didn't really think much of it, Several months later, the local FBI team came in and took all my computers, we had a short meeting with them about a year later, where they explained that I had hacked and then threatened that company, And then never heard from them again. This was back when I was using POP3 so I don't even have the email to know what I said, it may have have sounded like a threat, I honestly don't remember. My guess is shortly after my email something happened, and they found the email, which was through my ISP at the time, and contacted them assuming I had done it. As near as I can tell, they had logs that I visited the site, but nothing more as evidence.

      Anyways, my advise from this experience is to unfortunately keep it to yourself, be very careful when trying to be the good guy here. Since you've already started, you might be wise to contact a lawyer...

    4. Re:If you're in the United States, get a lawyer by Anonymous Coward · · Score: 4, Interesting

      Personally if it were me, I agree with the statement get a lawyer, but for different reasons. I'd immediately sue them. In a court of law you've now put them on the defensive. If they try to take legal action against you, you have that you discovered a flaw in their system, and immediately held them responsible. If they try to claim you were doing anything malicious, then they have to admit wrong doing and plead guilty to your lawsuit. And in your defense case, then it looks like you happened to find the flaw, was furious and took legal recourse against them.

      It may not make technical logic, but as far as I can tell in the legal world, putting them on the defensive as soon as possible is the best move you can do.

    5. Re:If you're in the United States, get a lawyer by bigtrike · · Score: 3, Informative

      The one time I ran into this, I informed the company from an anonymous email account. I claimed that I'd accidentally typed a number into the URL bar and someone else's complete order information came up. I stated that I had not shared the information with anyone and did not plan to (to cover my ass and make it clear I was not threatening them). I was still worried that they'd send the FBI after me, but I also felt that I had a moral obligation to inform them of the issue before someone else discovered it and stole a bunch of customer information.

    6. Re:If you're in the United States, get a lawyer by BitZtream · · Score: 2

      Regardless of your intentions, you may be treated as the wrongdoer here

      Not likely. Just because you've heard of some idiots who try to pretend they 'just accessed some urls' while stealing and republishing other peoples data doesn't mean that the FBI (who would handle such things) is a bunch of raving nutters.

      You're just being silly and making things up. Banks are regulated, they don't get to randomly freeze your account because they feel like it. Stop believing random crap you read on the Internet. The things you've seen reported on slashdot and other places are ALWAYS BS. Not entirely, but the story you hear is HALF the story. Its kind of like car accidents ... you can watch someone rear end another car on the street, and then they'll give you a story about how it wasn't their fault and it was the other guys and the give you all the right details to make it sound like they weren't at fault.

      Second, freezing your account to prevent you from paying a lawyer will just result in the lawyer filing a motion to get enough money to pay legal fees, and unless you're a complete and total jackass like Kim dotcom asking for millions, you'll get the money to pay your lawyer.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    7. Re:If you're in the United States, get a lawyer by ripvlan · · Score: 1

      Yes - this is always a sticky situation. "We" want to report the issue but have plenty of tales of people killing the messenger.

      My very serious solution - print out all of the details on a sheet of paper. Pop it in an envelop, drive to the next town, and mail it in.

      And use an older printer that doesn't put signature marks in the pixels. Or drive to a street, hike through the woods, to a payphone - and call them.

      You've done your job and aren't involved. Of course - you've already exercised the bug - they do have the logs and can go looking to see if anybody ever tried this. But maybe they won't, or at least maybe just maybe won't find you.

      You have a responsibility to keep it a secret.

      Plan B is to talk loudly at a hacker convention and let somebody else "stumble" across it.

  7. The responsibility of disclosure by clockwise_music · · Score: 2

    Troy Hunt has a great article here on the responsibility of public disclosure:

    http://www.troyhunt.com/2013/0...

  8. Re:It takes a scandal to fix this kind of thing IM by Anonymous Coward · · Score: 2, Insightful

    Too late...our anonymous submitted has already outed himself to the bank, and even if he hadn't, there should be enough of a trail in the server log to find it was him.

  9. Re:It takes a scandal to fix this kind of thing IM by CaptainDork · · Score: 1

    This is dead wrong. Bad advice.

    "Leaking" in this manner is a federal offense.

    The answer is to keep pressing and travel up the chain of command.

    Do not embed any compromising links in an email. Do not use email at all. Emails are discoverable in litigation.

    Use your own telephone. Do not involve your business.

    When you find a person who has a major cow when you tell them what you've found, give an example URL on the phone.

    Check the site now and then for compliance, but do it using someone else's junk. It sounds like you know how to do that.

    --
    It little behooves the best of us to comment on the rest of us.
  10. Re:It takes a scandal to fix this kind of thing IM by Noah+Haders · · Score: 1

    I personally have seen all kinds of cases where a disaster is required before anybody decides they want to harden their information security.

    That said, you might consider just leaking some of these documents to the open internet by simply pasting the URL to public places. For example, put it on twitter and give it an irrelevant but popular hashtag. Then it hits a major news site, and you know the rest.

    The trick is doing it without leaving a trail to yourself, otherwise you'll end up like those guys who found that AT&T link to the iPhone accounts.

    you know I think this was weev's approach to the att/ipad info leak, and look where it got him. although it turns out he was a scumbag doxxer, so no tears shed here.

  11. WTF? by Bill+Dog · · Score: 1

    In the meantime, I still have private financial information I consider to be publicly available. [...] So, Slashdot, how would you handle this situation?

    I'd certainly start by deleting my info there!

    --
    Attention zealots and haters: 00100 00100
    1. Re:WTF? by Neil+Boekend · · Score: 1

      How? The data is in the hands of the other. Would you propose hacking them to get that data off their servers? That might land them in legal hot water.

      --
      Well, I might have a way, but it only works on a semi spherical planet in a vacuum.
  12. Slashdot it by belmolis · · Score: 2

    Post the URL in a Slashdot article. There's a good chance a technical person in the company will read it. And since the site will be Slashdotted, you're probably not exposing any data. :)

  13. Immediately report the violation to legal by Anonymous Coward · · Score: 1

    Do not forward or show to anybody but legal.

    This are the kind of issues that can get you (and your company) in very nasty legal trouble. Reporting the situation to the legal depart of your company is your only SAFE option. Once you make the report do your best to destroy and sanitize yourself from the data (following company procedures).

    And just to be on the safe (semi-paranoid) side, keep a copy of all communication with legal including records of dates, times and name of everybody you talked too on the phone (about the subject).

    DO NOT CALL THE BANK. DO NOT DISCLOSE THE INFO TO OTHERS. CALL THE LEGAL DEPARTMENT AND LET THEM DEAL WITH THE SITUATION.

  14. Time to sever the financial relationship by Tillman · · Score: 3, Insightful

    Either the place is incompetent or made a deliberate design decision. Either way, your best move is to simply move on. There's plenty of competition out there.

    Do not reveal the information to anyone else, and don't go poking around.

  15. Contact the company's CSIO by ZipK · · Score: 2

    Try mailing security@companydomain.com. Follow-up on Monday by calling the company's headquarters and asking for the CSIO (chief security information officer). If neither of those work, ask to speak to the CIO's or COO's office.

  16. close your account with them by Anonymous Coward · · Score: 1, Informative

    Close your account with them. When they ask why. Tell them you assessment of their security procedures are bad and will be easily hacked. DO NOT GO ANY FURTHER THAN THAT. Leave it very vague and hand wavy. Under no circumstances tell them what is wrong. Leave that to someone else like what someone else suggested krebs or cert.

    Nothing will be done by them other than them getting mad at you. End the relationship with them.

    This pretty much is what will happen to you.
    http://www.slideshare.net/Lanc...

    They will follow the 5 stages of grief.

    The fact you trivially hacked them says they are not even aware they have an issue. Which means they will shoot the messenger.

  17. Re:Seems this has been done before... by mixed_signal · · Score: 2

    The folks that discovered the AT&T flaw downloaded information on something like 40,000 people and forwarded it to a journalist. Calling the institution itself after a spot check is pretty tame and seems well intentioned on its face compared to the AT&T situation.

  18. Please be very careful! by mallyn · · Score: 5, Informative
    Folks:

    Please be very careful if you discover something like this. Too many of us have been treated incorrectly by the company or the prosecuters.

    Here is what I would probably do:

    1. Remove all of my own assets from the company/institution.

    2. Verbally (phone or preferably in person) tell my family what I have done and suggest they do the same. As I can trust my family, I can say to them that I have been made aware of a possible security situation with the company.

    3. Verbally (in person if possible, phone as a last resore, not email) tell any friends THAT I TRUST about what I am doing and why and suggest to them they consider removing their assets. Do not go into any details of how I found out.

    4. Once out, stay out. Listen. Don't say anything to anyone else. If I feel that I must do something, I would stop; find an attorney whom I can trust (friend of a friend or family; not just out of the yellow pages). Pay them for an hour or so (which puts into place attorney client privilege) and tell them what is up. Fot God's sake, think twice, no three times before going this far.

    5. Shut up and go about your business.

    --
    Most Respectfully Yours Mark Allyn Bellingham, Washington
    1. Re:Please be very careful! by Anonymous Coward · · Score: 1

      I've got bad news for you.
      If those are the lengths you have to go to protect yourself against someone else's wrongdoings where you live you are most likely living in a fascism.

  19. Stop doing business with them by chromaexcursion · · Score: 1

    Talk to, call, or send an email to your boss If he's not an idiot things will end soon. If that doesn't work. If' you have a contract. read it carefully, find the exit clause and use it.

  20. You done fucked up by ArchieBunker · · Score: 4, Informative

    Every time someone has tried to be the nice guy its backfired. You see something like this? Keep your mouth shut and forget it even happened.

    --
    Only the State obtains its revenue by coercion. - Murray Rothbard
  21. Get off my lawn by fulldecent · · Score: 5, Interesting

    I was in a similar situation a few years ago. It involved write access to other people's brokerage accounts.

    FINRA, SEC, and FBI are all good points of contact and they have a straightforward complaint/action process. Assuming that you mailed a letter to the CEO first. Otherwise, I just now post live exploits to my blog at http://privacylog.blogspot.com... and usually give the vendor a heads up.

    You will not get credit for the find. The TLAs will not invite you to give a speech. You will not get a career out of this, or even consulting money. Your end game is getting the thing fixed and moving on. Do this by posting your story which proves how innocent you are and giving the people an honest chance to fix it. Imagine you are in front of a jury of idiots. If you are saying "I wrote down this URL, then I typed it back in and some else's bank records came up... then I found out I made a typo". This is a perfectly reasonable story, there is nothing to be afraid of.

    --

    -- I was raised on the command line, bitch

  22. TOR or Krebs unless you want a cellmate by Anonymous Coward · · Score: 1

    If you really want to do it yourself, plug the domain name in here (just the domain name, no "www." prefix) http://www.networksolutions.com/whois/index.jsp and send an email to the Tech and Administrative email contacts. Include the webmaster@ , security@ , abuse@ and postmaster@ addresses. If they have an Investor Relations contact email address or form, use it. The IR mailbox is watched very closely in all companies and is a better contact than trying to guess the CEO's email address. I have never had a note to the IR contact go unanswered for any problem.

    But use TOR to do it or go the Brian Krebs route. For the last incident response exercise I wrote for the bank where I work, the last paragraph was "The phone rings. It is a security blogger named Brian Krebs. He has found our information on a server in a foreign country."

    What was the most common question about the scenario from bank senior managers? "Who does this Brian Krebs think he is anyway?" Your worst nightmare, oh corporate one.

  23. It is not a bank or brokerage account. by 140Mandak262Jamuna · · Score: 2
    It is one of those mail-in-rebate houses. I am surprised there are people who still use them. The whole idea is a scam. To help them advertise a low low price, but small print reveals mail-in rebate to get the advertised price. I stopped using them long ago. They rely on consumers not bothering to send in the rebate coupons. Looks like now they allow the mail-in rebate to be claimed over the net, and the proof of purchase could be credit card statements.

    It is a security hole and all the dire warnings by others are true. Most of these companies are run by people with no IT or computer expertise. The top man is going to haul the IT dept on the carpet and demand an explanation. You think the IT chief is going to admit that he/she was running a moronic system? No, she/he is going to shift blame and find some convenient scape goat. Given the top honchos don't know much about anything other than their bonus calculation, IT chief is going to claim, "It is a hack! That guys hacked into my super secure site". Then the PHBs running the company would call in the lawyers and make a mess out of the situation.

    One thing the anonymous guy can do is to call the company that issued the mail-in-rebate and tell them, the outfit they had out sourced their rebate processing has holes in the system. Now it is the very big company that issued the rebate coupons run by PHBs fighting a smaller company that got the rebate processing contract run by PHBs. And quietly withdraw without drawing too much attention.

    --
    sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
  24. take it above EVERYBODY'S heads by ihtoit · · Score: 1

    Go directly to your FSA (or FBI) field office. This shit has the potential to cost MILLIONS if not dealt with IMMEDIATELY, and you could be implicated having knowledge of such vulnerability and not reported it to competent authorities.

    --
    Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
  25. You.will.be.blamed by MrKaos · · Score: 2

    Accept this, as you have uncovered something they didn't know and can potentially damage them.

    I did this with a government tax office and tried to alert them by calling the very number they advertised to handle this sort of issue. The response went like this:

    • Yeah there is a number you can call for this
    • There is a what in our what?
    • please provide you contact details

    The problem is, you want to help them and all they can see is 'random person the phone saying we have a problem' so it is easier to solve you. If the company is responsible enough to have a CERT team and a reporting mechanism you may stand a chance but it is more likely you will draw their ire because you can hurt the companies reputation.

    If you can't change institutions then you should consider establishing what their data privacy policies are, hire a lawyer and then frame legal action to protect your own data whilst seeking damages to the value of your life earnings for exposing you to identity theft and fraud. You should be pissed off.

    They won' t play nice so neither should you. Seek legal advice about the possibility for damages because you have been exposed to fraud. Leave it to them to discover the mechanism, because if they are that bad there are probably more.

    --
    My ism, it's full of beliefs.
  26. In their shoes by argee · · Score: 1

    You call and report this vulnerability. You think you are a hero. But look at it from their point of view.

    First they verify the problem, and its true. Now they know at least ONE person, you, knows about it. Do you think
    they are going to tell you "we been aware of it for three years, but no one knew..." or maybe "... we followed up on
    what you said, but it will be several weeks before we can fix it ..."

    Responding to you might lead more hacks. Consider you *already* reported it to Slashdot. If I was them I would
    work quietly on this and never respond to you. For all they know, you are ISIS.

    1. Re:In their shoes by Neil+Boekend · · Score: 1

      They didn't disclose any abusable data here.

      --
      Well, I might have a way, but it only works on a semi spherical planet in a vacuum.
  27. Rookie mistake... by Fallen+Kell · · Score: 4, Informative

    Well as others have already stated, you already made the rookie mistake of trying to report the issue and gave them your name and contact information. Now you are on the record as having breached their "security", even as pathetic as it is. When big money is possibly involved (as it would be in the case that financial information of hundreds/thousands of people are involved), you just became the "scapegoat". They will now use you as "hacking" them to attempt to make claims on their insurance to cover the cost of fixing the problem. That also means they will need to report to law enforcement, etc., to have the case brought forward.

    --
    We were all warned a long time ago that MS products sucked, remember the Magic 8 Ball said, "Outlook not so good"
    1. Re:Rookie mistake... by turning+in+circles · · Score: 1

      According to James Clapper, "Even more than terrorism, the threat of cyberattack is the biggest peril currently facing the United States". If Cybersecurity is a major threat to the US, you would think that some agency in the government would be interested in making it easy to report security flaws and not prosecute people for reporting security flaws. "And I said to myself, what a F&$#ed up world."

      --
      Might as well face it I'm addicted to data.
  28. Ass covering, BT Example from UK by Anonymous Coward · · Score: 5, Informative

    In the UK, British Telecom had a website that took donations for something. They left the website open, simply putting in a URL was enough to get to the private information of the donators.

    The man who discovered it was prosecuted for hacking their website:

    http://www.scl.org/site.aspx?i=ed832

    "He had visited the site and donated £30, but had become concerned at its slow response and what he had regarded as poor graphics. There had been extensive press coverage of “phishing” attempts and a number of these had involved fake sites masquerading as well-known UK financial institutions. His concern was that he had just provided details of his name, address and credit card and that these might be abused. Cuthbert sought to test the site by using a directory traversal test - in effect he re-formed the URL he could see in the command bar of his Internet browser to see whether the security settings on the remote Web site would allow him access beyond the web root. His attempt was rejected, he felt relieved and thought no more of the matter. "

    "But the test set off an alarm in an intrusion detection system (IDS) installed by British Telecom, the directory traversal being an obvious alerting signature. It wasn't difficult to trace him - he had just supplied his name, address and credit card details, and his IP address, which resolved to his employer, was captured both by the regular web-logs of the donation Web site and by the IDS. Cuthbert's subsequent interview with the Metropolitan Police Computer Crime Unit went badly. "

    1. Re:Ass covering, BT Example from UK by SmilingBoy · · Score: 1

      Not quite correct - he probed for a simple directory traversal (think adding "/../../etc/passwd" to the end of the URL). However, the website was not vulnerable and did not disclose anything! It only threw an internal alarm and Cuthbert was identified by the previously entered credit card information.

  29. Re:Rookie mistake... Also... by Fallen+Kell · · Score: 3, Insightful

    DO NOT DISCLOSE THE INFORMATION TO ANYONE ELSE!!!! I can't state that enough. Also, DO NOT ACCESS IT EVER AGAIN!!!!!! I also can't state that enough either. Any subsequent accesses/"breach" of their security will be blamed on you, and used as evidence that you sent others the information, since you were the only one who knew. Anything anyone else does will be painted as you working in conjunction with a "group of hackers" in an attempt to defraud others, or even possibly extort the company in some way. Any continued access attempts on your part will be used to show that it wasn't a onetime mistake that let you uncover the issue, and that you continued to "hack" the site over a period of time.

    --
    We were all warned a long time ago that MS products sucked, remember the Magic 8 Ball said, "Outlook not so good"
  30. Dan Cuthbert, UK by Anonymous Coward · · Score: 2, Informative

    Your thinking of Dan Cuthbert I think. A UK case, he donated money to a charity page then entered a directory traversal. Most likely /.. into the URL.

    http://www.scl.org/site.aspx?i=ed832

    (Slashdot is one dot away from a crime!)

    It was a real face palm moment for the British Justice system that they prosecuted him. In effect they said "a directory traversal would not have been authorized, therefore this is unauthorized use of a computer, hence a crime".

    A law designed pre-internet, yet the RFC for the web permits those URLs and their server provides the RFC interface therefore its for them to handle what data they return on what URLs. In this case they returned a 404 error page or similar. WHICH IS EXACTLY WHAT THEY SHOULD HAVE DONE, as per the spec.

    What point did it become a crime? When Judges the are also pre-internet get involved.

  31. Intent by TapeCutter · · Score: 2

    Agree. The AT&T mob were not hammered in court for finding a flaw, they were hammered because they attempted to use the flaw to extort money.

    --
    And did you exchange a walk on part in the war for a lead role in a cage? - Pink Floyd.
  32. Deal with someone else by FrozenGeek · · Score: 2

    Give them, maybe, one day to respond to your complaint. If they do not respond to your satisfaction, close your account and go elsewhere. It's your money. If they won't take good care of it, someone else will.

    --
    linquendum tondere
    1. Re:Deal with someone else by abies · · Score: 1

      Adn this will help exactly how versus his private details being available on unsecured webpage? Is process of withdrawing money somehow securing this data? We dont' know details, these things can stay there forever, even if he closes the account/stops dealing with them. Most companies/banks are not allowed to remove traces of anything happening for at least 5+ years.

  33. Confidence by Anonymous Coward · · Score: 2, Funny

    That's a confidential web forum that handles cases like this. Just provide the sensitive details and they'll take care of it from there. It's @ 4chan.org.

  34. Wikileaks. by BarbaraHudson · · Score: 1

    1. Send it to wikileaks.
    2. Send anon email to company saying the information has been posted tow wikileaks.
    3. Watch them have massive coronaries.

    --
    "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  35. Take Immediate and Thorough Action by DERoss · · Score: 2

    Send a postal letter to the CEO of the financial institution. Explain the problem. Give the institution a deadline for action. Since I found no actual disclosure of information in my case, I gave the institution a month. In your case, a week should be the maximum.

    If you do not hear back in a week, send a postal letter to the government agency that supervises the institution (e.g., SEC, Controller of the Currency, FDIC). Send a copy to the federal Consumer Financial Protection Bureau. Postal addresses are available online for such agencies.

    It helps if the institution's privacy policy indicates such disclosures are not permitted. In that case, insist that the government agency enforce the institution's privacy policy.

  36. Better Krebs than Weev by billstewart · · Score: 2

    You don't want to end up like Weev, even though they did eventually let him out of jail. And you're apparently not somebody who's got the kind of personality he has, which, while it may make you less likely to end up in jail, isn't necessarily going to get you off the hook either.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  37. e-mail, not phone by AndyCanfield · · Score: 1

    I would e-mail, not telephone. Phone calls are too short and simplified.

    Before you hit Send, trace through an exact example and describe every step in the e-mail message. I expect that the Customer Service Representative won't understand it. But with an e-mail he can forward it to somebody who will understand the security flaw.

    That's what I would do.

  38. /b/ by Lehk228 · · Score: 1

    use at least 14 proxies and post the details all over 4chan. the ensuing shitstorm will get the problem fixed PDQ.

    --
    Snowden and Manning are heroes.
  39. Better avenues that public disclosure by matthewv789 · · Score: 4, Insightful

    There are a few avenues I don't hear people talk much about using, which I think would be far more effective and appropriate, without the ethical issues of public disclosure (which I think is rarely ever justified). I'd strongly urge anyone to exhaust all these avenues before even considering the typical public disclosure of a flaw's vulnerabilities. I have a hard time thinking of ANY circumstance in which it would be ethical to publicize an unfixed flaw before there is clear evidence someone else is already exploiting it.

    1. 1. Try to notify technical contacts, who can most efficiently and cheaply understand and fix the problem, with the least embarrassment or hassle.
    2. 2. Notify the legal department, outside counsel, accountants or auditors. They are responsible for dealing with risks to the company, and to certifying proper controls over financial or customer information.
    3. 3. Try to notify executive management directly.
    4. 4. Contact government and other regulatory or certifying bodies, such as PCI (for anyone handling credit cards), SEC (for public companies), FTC, Better Business Bureau, Chamber of Commerce, etc.
    5. 5. Report it to CERT.
    6. 6. If you're a customer, (politely) threaten to take your business elsewhere (or actually do it), or have your attorney send them a letter threatening to sue for putting your information or money at risk. You could threaten to make it a class action too. (Note that you'd need to be an affected customer to have standing to sue.)
    7. 7. Any public disclosure you may be tempted to make, go through a news organization, who will verify the information, contact the company for comment, and weigh the ethical pros and cons of how to tell the story effectively without revealing so much information as to do harm. Some "on your side" segments on local TV news might work well for this.
    8. 8. If you want to publish or comment publicly yourself, consult your attorney, and limit yourself to saying that there is a vulnerability, but not any details about it. But you can particularly publicize the company's (non-)response to it.
    9. 9. If you can document that someone else is already exploiting the flaw, you could report on the exploitation that's occurring, without being the one to expose the vulnerability.
    10. 10. And of course once the flaw is fixed, you could discuss it more widely as well.

    (IANAL)

  40. Re:It takes a scandal to fix this kind of thing IM by Antique+Geekmeister · · Score: 1

    He apparently leaked information about 140,000 accounts. His sentence was vacated and conviction reversed on appeal because the appeals judge felt he should have been tried in his home state.

    It's too bad this judge was not available for the "Amateur Action" computer porn case in 1996 (http://fac-staff.seattleu.edu/mchon/web/Cases/thomas.html).

  41. Just name them anonymously by johncandale · · Score: 1

    Just name them anonymously, this is the only way executives move, bad press. Example, that time A UPS driver threw a TV over a fence. They guy had a video. At first they refused to pay to replace it, so he posted it to youtube and sent a copy to the 10 o'clock news. They paid up pretty fast. Their are tons of examples like this. You might think you are protecting people by hiding the bug, but you are not.

  42. Download some documents by drolli · · Score: 1

    and contact the persons whose privacy was violated in the documents. You probably can not sue, they can.

    Make sure to contact a lawyer first.

  43. Demand that your data gets taken down? by wonkey_monkey · · Score: 2

    I recently discovered that a partner web site of a financial institution I do business with makes it trivially easy to view documents that do not belong to me.

    Presumably, then, your data is viewable to others. First thing I'd do is demand that my data gets removed until the problem is fixed. Then I'd tell everyone who needs to know that I won't be uploading any more documents to this other website until someone else tells me I must, thereby taking responsibility for me doing so.

    Mind you, I'm in the fortunate position of having directors who take me seriously when I tell them things like that.

    --
    systemd is Roko's Basilisk.
  44. Profit! by righteousness · · Score: 1

    I would try to determine Step 2:

    1. Discover a web site disclosing private data.
    2. ???
    3. PROFIT!

    --
    Don't fornicate. Seriously, just don't do it.
  45. Slashdot, how would you handle this situation? by lippydude · · Score: 1

    Threaten to sue them and if they fail to act post details of the vulnerability. What's the name of this 'partner web site' again?

  46. 1 step sure-fire solution(?) by Demonoid-Penguin · · Score: 1

    Email the CEO, keep the body of the email short and simple enough for an IT illiterate to undestand the problem. Don't worry him/her about the consequences of the problem. Be sure to use a click bait subject line (they're probably very busy) e.g. Your account details for account [their bank account number] are attached. Don't forget to attach their bank account details

    Oh - and don't do any of this from your computer - or via your internet connection. And don't expect credit, just that the problem will be rapidly fixed - which is what you want, right?

  47. Laws are required by MobyDisk · · Score: 1

    Because the CFAA is being abused in this realm, major nations need to pass responsible disclosure laws that protect people who report security flaws so long as they follow proper procedure.

  48. Report them to CERT by MobyDisk · · Score: 1
  49. I would say "look until you find the CEO" by swschrad · · Score: 1

    but that's putting you in bed with the weasels.

    take some IT guys out for lunch with their laptop, show them how to lose their appetite. on a company computer.

    things will happen at a good rate of speed.

    if yoiu happen to have one of the security guys along, that will seal it quickly.

    --
    if this is supposed to be a new economy, how come they still want my old fashioned money?
    1. Re:I would say "look until you find the CEO" by MrBigInThePants · · Score: 1

      I would rather be a free weasel than an imprisoned, anonymous pauper.

  50. Move by AC5398 · · Score: 1

    Immediately move my accounts to another financial institution. Not only have they not dealt with the security threat, they have no procedure in place to immediately escalate security threats.

  51. Yes, get a lawyer by davidwr · · Score: 2

    As other replies have said, you are probably better off getting a lawyer BEFORE you go to the bank or anyone else.

    Why?

    1) If they've already discovered this themselves they may be working with the FBI and there may be a subpoena in your ISP's hands within minutes of you making your discovery.

    2) Even if there isn't, the veiled threat of prosecution can be very intimidating.

    3) By having your attorney speak to the bank and/or the government/police authorities for you BEFORE the police contact you, it will be abundantly clear to the police that you are just a good citizen and that it would be a political mess if they threatened to press charges or ignore the problem.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
  52. Try this ... by Rambo+Tribble · · Score: 1

    ... contact DHS and tell them you were at the library and you saw a guy with a scimitar and a Koran downloading private banking information. It will still likely be months before anything changes, but at least you'll know enough bankers are getting adequately inconvenienced in the affair.

  53. Web Programming 101 by g0bshiTe · · Score: 1

    I think that was covered in web programming 101 URL redirects/Directory transversal.

    --
    I am Bennett Haselton! I am Bennett Haselton!
  54. Answer by sgt_doom · · Score: 1

    You should have immediately contacted the FCC and FTC and Better Business Bureau!

  55. FBI! by EagleRider70 · · Score: 1

    I know others have said it, but, here is a link: https://www.ic3.gov/default.as... Going to law enforcement with the issue, should be a decent shield from prosecution. IANAL, so take this with a big grain of salt. So, maybe talk to a lawyer and ask them to file the complaint.

  56. Consider federal recourse, like the SEC? by whitroth · · Score: 1

    Letting Krebs know is a good idea... but email support at the bank, or even send the bank snail mail, with the info. Send it with delivery confirmation. And, at the bottom, add
    cc: SEC
    so they know you're serious. And really and truly, contact the SEC, which regulates banks, and esp. with all the bank problems lately, I'll wager they're really, really interested in this.

    Oh, call them back, and ask for "their legal service address". That will get someone attention, for real.

    Last option: get a lawyer to write a lawyer letter to the bank. This will also get their attention.

                  mark

  57. The locked door scenario by SmaryJerry · · Score: 1

    You suspect that a bank leaves the door to their building containing their customers money unlocked. Do you a) check to see if the door is open b) tell the bank it might be unlocked c) call the police? All of the above a) because the door doesn't say keep out anywhere b) because your money is in there c) because the banks negligence can and will cost you your money.