Slashdot Mirror


Kaspersky Customer Database Exposed

secmartin writes "A hacker has managed to gain access to several databases via a SQL injection vulnerability on Kaspersky's US website. He has posted several screenshots and a list of available tables; judging from the table names, the information available includes data on bugs and user- and reseller accounts. The hacker has indicated that no confidential information will be posted on the Internet, but since a large part of the URLs used was visible in screenshots, it will only be a matter of time before somebody else manages to duplicate this."

7 of 175 comments (clear)

  1. Awesome by Anonymous Coward · · Score: 5, Informative

    Our IT department switched us from trend micro to Kaspersky a few months ago. I haven't done any research on the merits or drawbacks of either, but what I do know is this:

    1) On our ancient desktop machines (Think 1.8ghz pentium 4's with 512 megs of ram) performance is a lot worse now than before we switched.

    2) Since the switch we've had some pretty serious downtime due to a virus got in on some old unpatched windows 2000 machines and then proceeded to wreak havok.

    3) SQL injection isn't that hard to prevent. Seriously.

    Granted none of that is enough to conclusively say that Kaspersky is a terrible product, the virus may very well have happened with Trend Micro as well, but as an end user my first impressions are less than positive.

    1. Re:Awesome by sqlrob · · Score: 5, Informative

      4) What were these doing accessible on a net facing computer? You can't hack what's not there.

  2. Re:Secure? Sure. by SanityInAnarchy · · Score: 5, Informative

    Since I don't have mod points... Just so you know, you're absurdly offtopic, and you're both wrong.

    Linux can't prevent a SQL injection attack. Not writing shitty software prevents SQL injection attacks, no matter what OS you're on.

    Linux is ready for the desktop, and is likely still easier to install than Windows. But the desktop is even less relevant to a discussion about a server-side SQL injection attack.

    --
    Don't thank God, thank a doctor!
  3. Re:oh well... by this+great+guy · · Score: 5, Informative

    No. Escaping is error-prone as you will invariably fail to escape some special character you don't know about. The right way to fix SQL injection is to use parametrized queries.

  4. Kaspersky does have its problems by Master+of+Transhuman · · Score: 4, Informative

    Overall, according to the testing agencies, it's a pretty decent AV with very high detection rates - almost always in the top five or ten.

    It's administration over a network is pretty complicated, using its Administration Kit. The basics aren't hard, but it's a very complicated product with a high degree of customization possible which makes administering it hard.

    It does have a bad problem with false positives - it seems to want to tag any exe encapsulated in an archive as a "trojan". I had a bunch of utilities for unattended installs of Windows sitting around and it went wild tagging a lot of them as "trojans" - even though most are well known utilities used for installing or slipstreaming Windows, and if any of them had trojans, somebody would have caught that by now. This is a know issue with KAV and apparently they're not doing much to correct it, according to comments on their forums.

    But ALL the virus engines these days are behind the curve of actual viruses in the wild - so it's no surprise that the occasional virus gets through. One got through on one of my client machines a week or two ago without being spotted by either KAV or Spyware Terminator. A very nasty one, too, that was almost a rootkit - took me some hours to fully get rid of it. Downloaded from a hostile Web site by one of the staff accidentally, I think, since the client has a hardware firewall in front of the network.

    --
    Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  5. mod_security by X.25 · · Score: 3, Informative

    I can't count number of time I've recommended usage of mod_security in order to prevent these types of crap.

    I can count, though, number of times people implemented it: 0.

  6. Re:oh well... by KermodeBear · · Score: 4, Informative

    So, the standard way of programatically querying databases, which is easier than building and escaping your own queries, and which makes you completely immune to SQL injection, is generally unavailable in a very popular combination of website technologies?

    Repton, you missed the part about the mysqli extension. A lot of functionality in PHP have been moved out into extensions. Enabling them is as easy as modifying the .ini file.

    I know that the poster above you was whining about it not being available on servers, but to be honest, I've never run into any (credible, reliable) hosting service that doesn't already have it enabled.

    And hell - if it is something that is good to have, why pick a host that doesn't have it?

    --
    Love sees no species.