Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Voice Over IP Under Threat?

Posted by Zonk on Fri Jan 05, 2007 10:11 AM
from the keeping-phone-calls-expensive dept.
An anonymous reader writes "The IT Observer is discussing the possible scary future of Voice over IP targeted viruses, and what that could mean for the consumer. The article discusses the likelihood that VoIP is going to become even more popular, and the damage that a targeted 'flash virus' could perpetrate in a very short amount of time. From the article: 'Let's imagine a scenario that could become commonplace in the near future: A user has an IP telephony system on his computer (both at home and at work). In his address book on the computer there is an entry, under the name Bank, with the number 123-45-67. Now, a hacker launches a mass-mailing attack on thousands or millions of email addresses using code that simply enters users' address books and modifies any entry under the name Bank to 987-65-43. ... If any of these users receives a message saying that there is a problem in their account, and asking them to call their bank (a typical phishing strategy), they may not be suspicious, as they are not clicking on a link in an email ... If they use their VoIP system to call the bank, they will be calling the modified number, where a friendly automated system will record all their details. ' "
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by Ingolfke (515826) on Friday January 05 2007, @10:14AM (#17473536) Journal
    is that people will call you up during your dinner to tell you that you're long lost uncle's oil wealth is available to you in Madagascar or about the wonders of this new herbal male health pill.
    • by HugePedlar (900427) on Friday January 05 2007, @10:18AM (#17473624) Homepage
      I wonder if VOIP might solve this to some extent. After all, with Asterisk or similar, the home user can set up an "Auto-Attendant", or menu system to filter calls that get through. Perhaps even some form of voice recognition (recognising people's voices in your address book, or, controversially, an Indian accent) might become common. I suspect VOIP will make the telemarketers' jobs harder in the end.
      • by arivanov (12034) on Friday January 05 2007, @11:02AM (#17474380) Homepage
        Exactly.

        I have been doing it for a while now (need to clean the code for the AGI plugin and post it). For my incoming phone lines I have scheduled times when the phone does not ring, when it rings only in my office for known callerIDs or when it rings for everyone who has not withheld their callerid. Trivial to do with asterisk+perl-AGI and quite more powerfull compared to the default autoattendant.

        The article brands all VOIP to be Skypelike (and vice versa). VOIP is not just PC based systems and this attack currently applies only to PC based systems. In addition to that it is limited to a specific VOIP system. A valid Skype attack is not applicable to Yahoo, MSN, SIP phones, etc.

        Things may change in the future when integrated contact management and click-to-dial becomes commonplace. This is not common enough now and can be found only on PHB/Sales laptops so it is not yet an attack vector that is worth mentioning. By the way, this will apply to any phone system that has click to dial, not just VOIP. Now having outlook+voip worm - that is a scary thought...
      • Perhaps even some form of voice recognition (recognising people's voices in your address book, or, controversially, an Indian accent) might become common.
        So you'd set up a filter especially to recognise and let through any caller with an Indian accent? That's a fine example of multi-cultural tolerance, it makes such a change from the usual racism on slashdot. Well done sir!
      • Re: (Score:2, Informative)

        Its YOUR uncle, and now YOU'RE no longer in need of correction.

        It's "it's your uncle" and not "its your uncle", and now you're no longer in need of correction, either. :)

  • by CommunistHamster (949406) <communisthamster@gmail.com> on Friday January 05 2007, @10:15AM (#17473542)
    This seems a logical progression of phishing, but it's hardly going to be a large impediment to the adoption of VOIP. Phishing hasn't dissuaded people from using email.
  • And that's why... (Score:4, Interesting)

    by AltGrendel (175092) <ag-slashdot@exNETBSDit0.us minus bsd> on Friday January 05 2007, @10:15AM (#17473554) Homepage
    ...I'm still using copper. I know that this will work itself out, that the technology will improve, etc, etc.. but until it does, I'm going to stay away from it. For me, it doesn't make sense to be an early adopter of VoIP.

    But that just my opinion.

    • The only reason I have copper is for E911 service and in case of power failure. I use my cellfone for 99.9999% of all calls even at home. I just like having a little redundancy in case of emergency.
      • The only reason I have copper is for E911 service and in case of power failure. I use my cellfone for 99.9999% of all calls even at home. I just like having a little redundancy in case of emergency.

        Exactly.

        Cell Phone for day-to-day calls.
        Cable Modem for day-to-day internet use.
        POTS for reliability when all else goes to heck.

        In the past ten years I've had both Cell and Cable fail and in each case I was able to fall back on POTS to handle my basic needs (and we're talking the center of a major urban metropoli

    • Not me man, I'm using copper AND VOIP.
    • Yes, I'm following the same strategy with email...
    • Re: (Score:3, Insightful)

      Don't worry, this article is mostly FUD. For one, it assumes that all phones will be vulnerable to the same flaws. They won't - they run MANY different code bases. There is no mono-culture in VoIP like there is with desktop operating systems (well, except for the Skype example - I don't use skype anyway due to the closed/proprietary nature of it.) It also assumes that any security flaws won't be fixed or addressed. Anyone that deals with IP phones knows that new firmware comes out every few months. If you h
    • Re: (Score:3, Insightful)

      I still use copper too. The copper in my coax cable which carries my internet traffic, and with it, my VOIP calls. Of course, what this article is talking about is people who use autodialers of one kind or another - which includes cell phones, PBXs with click-to-call, Skype, etc - it's got nothing to do with VOIP as a technology for transmitting the voice data. My VOIP solution uses a perfectly normal phone, not a computer, and so until Uniden and VTech start issuing vulnerability warnings I think I'm OK.
  • I have to say that using malware on VoIP hopes but cannot assume that VoIP is even functional and stable enough to do that. Maybe other people have a different experience but CallVantage is not ready for primetime and if they want to use it for exploits and malware they'll have to compete with the utter crappiness of the service that works like malware all on its own.
  • by Doc Ruby (173196) on Friday January 05 2007, @10:17AM (#17473582) Homepage Journal
    Who's got an OSS Flash or Java applet that is a SIP or IAX client? If we keep the VoIP SW on the server (tested and upgraded), and give it access to our network/AV HW only on request in a sandbox, we're pretty safe against viruses. These applets can be signed and distributed easily, unlike OS-installable full apps, or dedicated HW.
      • OpenWengo is an OS-installed app, not an auto-installed downloadable app maintained on the VoIP server. Their Flash applet is closed source.

        If the distribution and maintenance process is slowed down by requiring users to install (continuously bugfixed) apps under their OS, the ecosystem will remain riddled with insecurity.
  • by Rastignac (1014569) on Friday January 05 2007, @10:17AM (#17473594)
    Spams in my inbox is painfull. Spams using VoIP will be very very painfull.
    VoIP will be cheap enough for spammers, and easy to handle by spamrobots...
  • by Raistlin77 (754120) on Friday January 05 2007, @10:17AM (#17473596)
    I would say there are likely far more people who use regular landlines and cell phones and don't use VoIP, but that do still maintain phone books on their computers. If they call with their regular phone, the same will occur. Why drag VoIP into the cross-hairs alone?
  • by crazyjeremy (857410) * on Friday January 05 2007, @10:18AM (#17473604) Homepage Journal
    This seems to be a misleading article. Most phishing techniques do not use elaborate setups as suggested. They use very simple techniques. Oddly enough, the article author seems to agree.
    Evidently, this would require a large degree of innovation, research and development on the part of the creators of malicious code, and I genuinely doubt that they would bother.
    The potential scenerio quoted in the post is so far fetched, it's doubtful anyone will ever pull it off. It involves hacking their voip system, home computer (and address book), a mass-mailing spam which happens to also include the email address of the hacked computer, user intervention (they must read the spam and respond), and the hacker must also have a good enough radio voice to fool the homeowner into thinking he's actually calling his real bank. Don't know about you, but we're not to afraid of this possible Voice over IP threat.
    • The potential scenerio quoted in the post is so far fetched, it's doubtful anyone will ever pull it off. It involves hacking their voip system, home computer (and address book), a mass-mailing spam which happens to also include the email address of the hacked computer, user intervention (they must read the spam and respond), and the hacker must also have a good enough radio voice to fool the homeowner into thinking he's actually calling his real bank.Don't know about you, but we're not to afraid of this possible Voice over IP threat.

      Far fetched? Hey, the author thought it up, didn't he? Everything is far fetched (sailing around the world, explaining gravity, travelling into space) until someone actually does it. This technique requires thought and some actual work. So? If there's money in it, someone or some group out there with the wherewithal and time on their hands will try and exploit it, because basically they know your average computer users are sheep, and they have these nifty shears. It's this kind of complicated and non-obvi

    • Also, that the phisher has figured out WHICH bank this particular person uses, and has set up a phone number/system specifically for that bank. Hearing the message "Thank you for calling THE BANK" might be a tip-off that something's up. ...And all of this without leaving enough of a trail that they'll be caught.
    • Far fetched? Not really. Difficult to pull off and thus unlikely due to not being the low hanging fruit? That's more like it.

      This "technique" is already possible. A mass mailed email worm (or whatever) modifies the user's "hosts" file (C:\WINDOWS\System32\Drivers\etc\hosts) so that www.paypal.com gets pointed to his or her IP address. The usual precautions the victim would engage in wouldn't apply, as the victim would actually be going to the website directly (rather than clicking on a link in an email)

  • And if I go out at night, and if I wear all black, and if a car comes towards me with no headlights on then I might get run over.

    Seriously though, there were an awful lot of 'if's and 'maybe's in that, and at least one of those steps can be avoided by being at least slightly knowledgable about the internet. It's a matter of education and in that respect people have to help themselves, or other people will help themselves instead.

    To all your money.
  • This is just the same problem as before, only people aren't expecting it. A lot of people fell victim to phishing scams (and many still do), using email, because they are stupid. I guess this is a little more advanced, since people expect certain speed-dial numbers to not change. Granted they could probably just have a system where the bank has a password that they have to tell you, so that you can verify that you are actually talking to the bank. This is probably a good idea anyway, as it would be easy
  • Not Unique to VOIP (Score:4, Informative)

    by mmurphy000 (556983) on Friday January 05 2007, @10:22AM (#17473690)

    Changing phone numbers in an address book isn't unique to VOIP. A virus could scan Outlook and other common address book systems and change phone numbers, whether VOIP or not. Since most people don't have their bank phone numbers memorized, they'll assume that the address book entry is correct. Even if they use a non-VOIP phone, the phishing attack can work.

    Now, a VOIP system might have an integrated address-book/speed-dial system that could also be attacked. But otherwise, I don't see where this is unique to VOIP.

  • I too, can come up with lots of non-scenarios based on speculation...

    What if someone hacks the telephone exchange and redirects all calls to the bank to a new number?

    What if I get a letter from my bank saying they have moved, and a phisher builds a new bank at that address, thus allowing them to take all my details?
  • Someone please explain how a virus can update a Skype user's telephone book? Seems like a poorly-designed software that allows voice telephone messages to modify its database.
    • Because we all know, no major software has undiscovered bugs, buffer overflows, yadda, yadda. Linux, Firefox, Apple, Microsoft, never put out patches for newly found security holes because all their software is well-designed.

      What color is the sky in your world?
    • "Someone please explain how a virus can update a Skype user's telephone book? Seems like a poorly-designed software that allows voice telephone messages to modify its database."

      Easy. The skype user's telephone book is most likely (I don't use Skype so I can't be sure) a file on their PC.

      A virus can enter that PC in any of the normal ways that they can propagate and go modify that file. (i.e. it isn't a "VoIP Virus", it's a traditional virus that attacks your address book once you're infected)
  • by Sneakernets (1026296) on Friday January 05 2007, @10:25AM (#17473754) Journal
    "Steve... send the PHONE SPIDERS."
  • This is the price we pay for a computing monoculture. Don't use Windows, this won't happen. Yes this is Microsoft's fault, BUT, to be fair, this would happen to a certain extent with any computing monoculture. So:
    • Don't use Windows
    • Don't all move to the Mac
    • Don't all use one OS environment - replacing Windows with everyone using the same version of xyz linux wouldn't help that much
    • Don't all use the same CPU (x86)

    and all this should go away. When did you last hear of a security breach on Alcatel DEC

    • by solevita (967690) on Friday January 05 2007, @10:42AM (#17474096)
      I've seen this argument crop up regularly on /. recently, but that doesn't make it a good one. Why? Well lets extend your argument to its logical conclusion - not only should we all use different operating systems, web browsers, CPU architectures, but we should all also use different file formats, standards and networking protocols.

      I'll never get caught by a phising scam because my web browser doesn't support the HTML used on fake-paypal.com and I can't even connect to it anyway because I'm using a brand of TCP/IP used only by myself and a handful of /. geeks.

      Call me crazy, but I want to work on something that I can easily share with my colleagues - I want the most open digital environment I can get.

      I refuse to accept that lazy/poor programmers can excuse the security holes in their products by claiming that everyone should be aiming for security through obscurity. Lets stop blaming Windows/Internet Explorer users for the insecurity of the products they use. Security through diversity is just renamed security through obscurity; it's no security at all.
    • by planetmn (724378) on Friday January 05 2007, @10:45AM (#17474128)
      WTF?

      Now, I understand in the Slashdot world, anything that pokes at Microsoft and Windows is instantly thought of as insightful and true, but what the hell does this problem have to do with Microsoft? This problem exists because of social habits of human beings. Most phishing scams work only when there is action taken by a victim that is either uncaring, or doesn't know better.

      I recently received a phishing scam email from somebody purporting to be Wells Fargo Bank. First clue is obvious, I don't have an account with them, but I was curious. So I clicked the link in Firefox. The site comes up, looks similar to the real Wells Fargo site, but has a completely non-legitimate URL. So then I clicked the link in IE7. Guess what, IE7 knew it was a phishing site.

      So in my above example, Microsoft was not at fault, in fact, they were proactive enough to protect the user. Stop blaming third parties for what amounts to human error. And if you think OS diversity would help the problem, you are wrong. People react the same way to phishing scams regardless of OS.

      And your suggestions are absolutely insane. One thing that computing monoculture brings is a standard implementation. How would the average consumer react if they were told "this software won't work on this OS" or worse "this software only works on certain flavors of linux, but not yours". The reason the PC grew so quickly was the ability to choose between different software and hardware easily, and be sure of compatibility. Sure, niche markets existed, such as the Mac, but the PC was much more extensible and much more desirable.

      -dave
      • Now, I understand in the Slashdot world, anything that pokes at Microsoft and Windows is instantly thought of as insightful and true, but what the hell does this problem have to do with Microsoft?

        The attack described relies upon a worm that can compromise desktop systems. Worms are a lot easier to implement if their are a huge number of identical targets with identical holes. Currently that target is Windows.

        This problem exists because of social habits of human beings. Most phishing scams work only whe

          • Or, it would only require a user to run certain software, which is the reason a lot of people get malware/spyware on their computers in the first place.

            Yeah, trojans are a problem, although all the studies I've seen by number of infections put malware without user interaction in the lead.

            This would not stop if there were no holes. It would only stop if there was a way to ensure that people didn't run software they download AND that any software provided to them was legitimate.

            OS's don't need to pr

  • This is a concept at best. A virus going through peoples' cell phones (which are far more in use than VoIP sets) to do the same thing is even more viable. This is another 'exploit' that relies on people to be completely oblivious to what their technology is doing. I agree that it is a problem, but it has nothing to do with VoIP. A lot of PHBs are already afraid enough of 'voices in the network' without somebody throwing 'OMFG What if?!' at them.

    OMFG, What if someone wrote a virus that relinked your favorite
  • I think that this type of attack is still, to a large degree, depending on TCP vulnerabilities. This type of malware is going to be highly dependent upon other things to initiate such attacks. Granted, in the case of Skype or other PC-based applications this will be far easier to accomplish. I'm not sure it's a VoIP issue so much as an issue of we need to be aware of yet another medium for the transport of exploits. VoIP is UDP based. Protection of such voice streams, should malware over VoIP become pervasi
  • ...Let's imagine a scenario that could become commonplace in the near future

    Or sooner now they have described what to do & /. has noted it (assuming of course script kiddies and crackers can read) and scripted kiddies are reading it....

    Jaj
  • What about a BotNet? (Score:3, Interesting)

    by bhsx (458600) on Friday January 05 2007, @10:40AM (#17474052)
    A serious botnet can have 50k-100k minion boxes out there... Imagine if VOIP hit even 20% penetration, that would obviously be 10k-20k phones that botnet owner has access to. If you were the type of slimeball or, gods forbid, terrorist, what would you do with 20 thousand phones you had access to? Think DDOS on 911? Think maybe just dialing pay phone services like the old auto-dialer spyware? People maybe shouldn't be allowed to run their VOIP systems on just any old machine... Perhaps all those writing VOIP code for Windows systems should just stop and burn all copies of their apps? That doesn't sound too bad :P

    • A 911 center typically has a handful of human operators - so what is needed to DOS a typical PSAP is a handful of cell phones and you just have a few people phone in and the 911 center is totally full. You don't need a bot net of voip systems. The reason this does not happen is because there is very little incentive to DOS a 911 center.
    • Ugggh.

      I'll keep it brief. As other informative posts have explained, the virii potential of VOIP clients is unlikely.

      Say I'm a bad guy and I want to simultaneously call 100,000 machines. I would have to spawn 100,000 connections to a voip server. Your voip server firewall has a threshold for dropping connections from a single IP address doesn't it? If the bad guy is using 100,000 zombies then the problem is not voip is it?

      Let's say for a minute that I'm able to connect to a client. *The phone will ring
  • by Opportunist (166417) on Friday January 05 2007, @10:43AM (#17474098)
    Let's face it, who's the prime target for phishing? Joe Average Users. "We" (as in, people who enjoy technology as a pastime more than just a tool) know about such problems, and we know how to deal with them. I still never heard of a 'clued' person to become a phishing target. We certainly don't answer to mails akin to "Hi, I'm your Bank, please send me all your details in reply or your account will be frozen", and we usually routinely check for unwanted BHOs and tasks, and we certainly run up to date AV software (or at least have another reason to assume with some sort of faith that we are not infected).

    In short, we know the threat. And we're also the ones who use VOIP predominantly, aside of companies (who better have someone like us as their IT-security person there). Auntie Mable and Joe Hicksberger won't switch to VOIP any time soon.

    So personally, I'd rate THAT threat low. At least for now.
  • Dammit don't you think the phishers read Slashdot too?
  • viruses over a virus from a public pay phone anyday!

    Those shankers hurt!
  • This is all hype in my opinion. There probably will be attacks against VOIP banks but they won't be as mentioned. Each VOIP Provider has their own code they use, I don't see how one virus is going to spread through more then the one system it was designed on/for. The attacks will be denial of service attacks most likely.

    • I haven't called my bank in over a year. I haven't found anything I can't do online yet. I even got a certified cheque to close on a house without talking to anyone.
      • While my bank has quite a few online services, it appears that many require a phone call or in-person visit.

        Of course, since my bank has a branch office right next to my company's cafeteria, I don't consider this an issue. :)

        I don't store numbers in any address book that are on websites I frequently use, this includes all of my banks. (100% of phone calls to the bank are usually the result of a "you can't do this online, call 1-800-xyz-abcd".
    • Re: (Score:3, Insightful)

      It's not at all a bad thing to have in your phone's address book. Say you are on a trip and your wallet gets stolen, etc. You may want to call your bank, credit card company, etc, very quickly to put stops on your accounts.