Stories
Slash Boxes
Comments

SoylentNews is people

posted by CoolHand on Friday November 27 2015, @11:12PM   Printer-friendly
from the injection-infection dept.

One of the hackers suspected of being behind the TalkTalk breach, which led to the personal details of at least 150,000 people being stolen, used a vulnerability discovered two years before he was even born.

That method of attack was SQL injection (SQLi), where hackers typically enter malicious commands into forms on a website to make it churn out juicy bits of data. It's been used to steal the personal details of World Health Organization employees, grab data from the Wall Street Journal, and hit the sites of US federal agencies.

"It's the most easy way to hack," the pseudonymous hacker w0rm, who was responsible for the Wall Street Journal hack, told Motherboard. The attack took only a "few hours."

But, for all its simplicity, as well as its effectiveness at siphoning the digital innards of corporations and governments alike, SQLi is relatively easy to defend against.


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: 3, Interesting) by MichaelDavidCrawford on Saturday November 28 2015, @01:10AM

    by MichaelDavidCrawford (2339) Subscriber Badge <mdcrawford@gmail.com> on Saturday November 28 2015, @01:10AM (#268924) Homepage Journal

    TCP has had out-of-band signaling since the very beginning - urgent data.

    At one time, building a simple circuit that generated a 2600 Hz tone, conventionally packaged in a red or blue box, would yield the in-band signal for dropping an Amercian five-cent piece into a payphone. How much did the phone phreaks actually cost anyone by calling Brazil for three days? Even so, Ma Bell instituted out-of-band signalling, that's why your connection is briefly cut off when you pop in a quarter.

    We have SQL injection because, out-of-the-box, SQL databases only provide in-band signaling. Surely there is a wrapper somewhere that takes care of this? You could have two text I/O queues, in gets the SQL the other gets the payload data and it is simply not possible to get through that wrapper without the two being separated.

    It's quite telling, now that it even occurs to me, that in twenty-eight years as a software engineer no one has ever asked me what SQL injection was. Not in job interviews, not on the job, not even outside of work.

    --
    Yes I Have No Bananas. [gofundme.com]
    Starting Score:    1  point
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 1, Informative) by Anonymous Coward on Saturday November 28 2015, @02:59AM

    by Anonymous Coward on Saturday November 28 2015, @02:59AM (#268963)

    No, out-of-the-box all modern SQL databases/libraries support parameterized statements, which is the SQL version of out-of-band signalling. You write the statement with placeholders for the user provided values and then provide those values in a separate argument from the query string. You could have a check that you only call SQL library functions with query strings that are compile-time constants to make sure this isn't messed up. Or you could use an ORM and never write SQL directly.