Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Saturday August 27 2016, @06:07PM   Printer-friendly
from the don't-go-through,-go-around dept.

Earlier this summer, the team at Inversoft published a comprehensive and sophisticated guide to user data security. The guide spans from hardening servers from provisioning, up through the IP and SSH layers, and all the way to application-level techniques for password hashing, SQL injection protection, and intrusion detection. As proof that they stood behind their advice, the Inversoft team provisioned a pair of Linode hosts, a web server and database server, and gave them the hardening treatment. Inversoft offered up a fully-loaded MacBook to anyone who could break in, taunting all comers by naming the hardened web server hackthis.inversoft.com.

Game on.

Needless to say, they found a way in.

[...] After discovering an unpatched, unfirewalled Elasticsearch instance using nmap, we gained shell access on a utility server used for various functions at Inversoft. On there, we found API keys for Linode left behind by a human operator. Those keys allowed us to detach disks from running servers and attach them to servers we controlled, stealing sensitive user data (all to win a prize).


Original Submission

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 4, Insightful) by frojack on Saturday August 27 2016, @06:22PM

    by frojack (1554) on Saturday August 27 2016, @06:22PM (#393994) Journal

    More In the Box thinking on the part of the defenders, and some rule-stretching by the attackers.
    Bravo!

    It goes to show just how vulnerable everything is due to the intertwined nature of everything Digital. Best practices still leave vulnerabilities laying around.

    The password, and its "high-tech" cryptographic offspring, is probably the single biggest security blunder the entire industry has made. The whole concept is due for some out of the left field new idea to come along and change everything. I have no clue what it will be, but it can't come soon enough.

    --
    No, you are mistaken. I've always had this sig.
    • (Score: 4, Insightful) by Anonymous Coward on Saturday August 27 2016, @08:37PM

      by Anonymous Coward on Saturday August 27 2016, @08:37PM (#394030)

      I have no clue what it will be, but it can't come soon enough.

      It can fuck right off if it involves fingerprints or other such nonsense.

    • (Score: 2) by Scruffy Beard 2 on Saturday August 27 2016, @08:58PM

      by Scruffy Beard 2 (6030) on Saturday August 27 2016, @08:58PM (#394037)

      Public key encryption has some feature passwords lack.

      For example, I am considering encrypting my back-up in transit. Instead of sending the encryption key separately, I can simply encrypt them with the back-up server's public key.

      The private key would be encrypted with a long passprase that I carry with me. The passphrase alone will not decrypt the data though.

      • (Score: 3, Insightful) by DrkShadow on Saturday August 27 2016, @09:06PM

        by DrkShadow (1404) on Saturday August 27 2016, @09:06PM (#394039)

        After discovering an unpatched, unfirewalled Elasticsearch instance using nmap, we gained shell access on a utility server used for various functions at Inversoft. On there, we found private keys for Linode left behind by a human operator. Those keys allowed us to detach disks from running servers...

        Public key crypto has the same drawbacks as API keys being left around: if you have the private key, you have everything. I bet you don't even password-protect your private keys ...

        • (Score: 3, Touché) by gnampff on Saturday August 27 2016, @09:30PM

          by gnampff (5658) on Saturday August 27 2016, @09:30PM (#394042)

          You lost the bet. Please consider reading the last of the three lines your were replying to. Something about a long passphrase for the key :)

          • (Score: 0) by Anonymous Coward on Sunday August 28 2016, @05:55AM

            by Anonymous Coward on Sunday August 28 2016, @05:55AM (#394111)

            I see the words "would be" not the word "is."

        • (Score: 2) by Scruffy Beard 2 on Sunday August 28 2016, @04:33AM

          by Scruffy Beard 2 (6030) on Sunday August 28 2016, @04:33AM (#394098)

          While I have not implemented it yet, I was thinking the private key would exist only on the back-up server. If the key is lost, the data on the server is probably gone as well. Any (optional) second server would have its own private key.

          Where I think encrypting your key is a little pointless is when you are backing up your keys (not the case in the scenario above). If you use a passphrase protect your secret keys, you need to store the passphrase somewhere. Encrypting the key with a passphrase also prevents m of n key distribution schemes.

          And yes, the PGP or GPG file on a computer in active use should have the keys encrypted with a passphrase.

          • (Score: 2) by Scruffy Beard 2 on Sunday August 28 2016, @04:37AM

            by Scruffy Beard 2 (6030) on Sunday August 28 2016, @04:37AM (#394099)

            Maybe the confusion arose because I was using a "server" to refer to a machine with no direct network access.

            Sneakernet [wikipedia.org] FTW!

  • (Score: 2) by dingus on Saturday August 27 2016, @07:39PM

    by dingus (5224) on Saturday August 27 2016, @07:39PM (#394015)

    I guess the moral of this story is to not trust VPS providers, because it seems to me that the ones who fucked up this time around were linode.

    • (Score: 2) by dingus on Saturday August 27 2016, @08:00PM

      by dingus (5224) on Saturday August 27 2016, @08:00PM (#394023)

      nvm I read it wrong. Ignore.

  • (Score: 3, Insightful) by Username on Saturday August 27 2016, @07:46PM

    by Username (4557) on Saturday August 27 2016, @07:46PM (#394017)

    How do you harden a network without checking open ports? It seems like one of the first steps is to see what is accessible by WAN or WLAN.

    • (Score: 5, Informative) by frojack on Saturday August 27 2016, @08:16PM

      by frojack (1554) on Saturday August 27 2016, @08:16PM (#394028) Journal

      I fail to see how that matters, since they found keys to the server on another server in a totally different location.
      Like breaking into your house to steal the keys to your office.

      --
      No, you are mistaken. I've always had this sig.
      • (Score: 0) by Anonymous Coward on Saturday August 27 2016, @08:42PM

        by Anonymous Coward on Saturday August 27 2016, @08:42PM (#394031)

        Seems more like a lack of dogfooding by the people who put together the security paper and servers.

      • (Score: 1) by fubari on Saturday August 27 2016, @08:43PM

        by fubari (4551) on Saturday August 27 2016, @08:43PM (#394032)

        frojack: Was going say this, so +1 instead.

        all: TFA is a fascinating read, and frojack's home vs. office metaphor is quite good.

  • (Score: 3, Interesting) by Anonymous Coward on Saturday August 27 2016, @09:33PM

    by Anonymous Coward on Saturday August 27 2016, @09:33PM (#394044)

    OK, so what we can learn from this?

    a) All your machines must be at the "same level" and "separate"? IE, no weak link, all strongholds, no exceptions. Including "jack of all trades" or "test" ones. If not needed, off?

    b) Keep "passwords" and other "keys" offline/cyphered as much as possible? If the system insists keeping things visible (crap system), find a workaround like a cyphered mount?

    c) Limit connections to well known machines? IE, don't talk to anyone not intended.

    d) Disallow unsupervised automation as much as possible? Like the IP swap, etc. See c) question.

    More? Yes, I know, it will never be perfect (I have not mentioned social engineering or 0-days, eg) but I am talking about learning how to do it better.

  • (Score: 0) by Anonymous Coward on Sunday August 28 2016, @07:10AM

    by Anonymous Coward on Sunday August 28 2016, @07:10AM (#394118)

    I mean really how do you expect to attract professionals without proper compensation? Long gone are they days of yore when people cracked things just for the fun of it, now when you get an infection you don't notice an ambulance driving around your screen but instead your bank balance going to 0 or -50000...

  • (Score: 2) by migz on Sunday August 28 2016, @08:27AM

    by migz (1807) on Sunday August 28 2016, @08:27AM (#394134)

    This is the front door, not the back door. They literally used the legitimate keys to gain access.

    • (Score: 0) by Anonymous Coward on Sunday August 28 2016, @09:00AM

      by Anonymous Coward on Sunday August 28 2016, @09:00AM (#394145)

      Oh. Good to see their network is still rock solid then - oh wait, no it isn't.