Slashdot Mirror

← Back to Stories (view on slashdot.org)

Attackers Install DDoS Bots On Amazon Cloud

Posted by timothy on from the fully-buzzword-compliant dept.

itwbennett (1594911) writes "Attackers are exploiting a vulnerability in distributed search engine software Elasticsearch to install DDoS malware on Amazon and possibly other cloud servers. Last week security researchers from Kaspersky Lab found new variants of Mayday, a Trojan program for Linux that's used to launch distributed denial-of-service (DDoS) attacks. The malware supports several DDoS techniques, including DNS amplification. One of the new Mayday variants was found running on compromised Amazon EC2 server instances, but this is not the only platform being misused, said Kaspersky Lab researcher Kurt Baumgartner Friday in a blog post."

14 of 25 comments (clear)

  1. Is the AWS cloud... by digsbo · · Score: 2, Funny

    Is the AWS cloud so powerful that it can create a DDOS botnet that it cannot withstand?

    1. Re:Is the AWS cloud... by i+kan+reed · · Score: 2

      Easiest DDOS ever: install a worm that makes the targeted site take part in a DDOS, and get disconnected as a security measure.

    2. Re:Is the AWS cloud... by alen · · Score: 2

      being that amazon charges you for incoming and outgoing data, i don't think they really care

  2. Only a problem for unpatched systems? by timrod · · Score: 4, Insightful

    The article claims that only 1.1.x versions of Elasticsearch were vulnerable, and that the vulnerabilities were fixed in 1.2.x and 1.3.x. To me, this sounds like any company still running 1.1.x versions brought it upon themselves.

  3. But it's the cloud... by houstonbofh · · Score: 4, Funny

    But it's the cloud! I don't have to worry about things like software updates and patching!

    The more things change...

    1. Re:But it's the cloud... by Richard_at_work · · Score: 4, Interesting

      If you choose a cloud offering which does that for you then yes, you don't have to worry about things like software updates and patching.

      However, if you choose a cloud offering which is essentially a hosted server, then you still have to worry about all the things you would with your own local server, excluding power and hardware faults.

      Amazon AWS is a platform provider, its not a fully managed solution and never has been - people have been caught out by that before when availability zones failed and suddenly people realised the benefit of having redundant instances in multiple availability zones.

    2. Re:But it's the cloud... by houstonbofh · · Score: 2

      If you choose a cloud offering which does that for you then yes, you don't have to worry about things like software updates and patching.

      I would say you still have to worry about it, and verify it was done. You just do not have to actually do it...

    3. Re:But it's the cloud... by DivineKnight · · Score: 3, Funny

      Quiet you. A few more revolutions around this sun, and we'll own this planet. We've all but convinced them that they need to move everything onto the cloud, and soon thereafter that they need to upgrade to this year's CPU: ARM (preferably v6). Those of us who are quietly stashing those gigantic x86 16-core / 4 CPU beasts that companies are throwing away because 'IT & programming are last year's business' are sitting pretty for the upset that is to come...I mean, we are looking at a "Napolean won Waterloo" level of misreporting style event, and it feels good.

    4. Re:But it's the cloud... by turbidostato · · Score: 3, Insightful

      "If you choose a cloud offering which does that for you then yes, you don't have to worry about things like software updates and patching."

      Well, yes, you need to worry anyway.

      If it's not done, because it's not done. But if it's done, because of what the update/patching breaks on your own apps.

  4. Oh, Look! A red herring! by houstonbofh · · Score: 3, Insightful

    So a bunch of virtual machines were compromised that happened to be in one location where they looked. KILL AMAZON! Sigh...

  5. Re:Oh, Look! A red herring! by i+kan+reed · · Score: 3, Funny

    Look, slashdotters are terrified of change. If you don't like that, go somewhere else.

    Except that's changing things, so please don't; it's too scary.

  6. Stupid sensationalism by Imagix · · Score: 4, Insightful

    So why is Amazon being specifically mentioned here? What makes this specific to Amazon? Is Google Compute Engine somehow immune to this? Or Azure, or any other hosting provider? Or self-hosted? Better headline: "Servers compromised through known vulnerability, admins failed to update software to close vulnerability."

    1. Re:Stupid sensationalism by Anonymous Coward · · Score: 2, Interesting

      My guess is they just looked at a couple EC2 machines, and since no one uses Azure or Google Compute Engine, they just didn't bother following up on those and made a blanket statement that it applies to all environments (which it does). This has nothing to do with EC2, or Azure or any other environment, really. This is a vulnerability in a piece of 3rd party distributed search engine software that a bunch of people were too lazy to update.

      The real headline just doesn't perform quite as well as the clickbait they came up with.

  7. Re:EC2 servers already fire walled by jafiwam · · Score: 2

    I have had so so many hack attempts from Amazons servers that it was just easier to fire wall ALL of them.

    Yup. Amazon Cloud and a couple others are completely null routed from my work network. Big sections of others overseas are blocked as well.

    So far, complaints have been zero. And, we get less log and web site form harassment from misbehaving bots.

    We have determined that the signal to noise ratio coming from cloud hosting services is ZERO.