SoylentNews is people
SoylentNews
SQL Injection Attacks Represent Two-Third of All Web App Attacks
For its "State of the Internet" report, Akamai analyzed data gathered from users of its Web application firewall technology between November 2017 and March 2019. The exercise shows that SQL injection (SQLi) now represents nearly two-thirds (65.1%) of all Web application attacks. That's up sharply from the 44% of Web application layer attacks that SQLi represented just two years ago.
Local File Inclusion (LFI) attacks, which, like SQLi, are also enabled by a Web application's failure to properly validate user input, accounted for another 24.7% of attacks. Together, SQLi and LFI attacks represented 89.8% of all attacks at the Web application layer over the 17-month period of Akamai's study.
[...] SQL injection errors and cross-site scripting (XSS) errors have topped, or nearly topped, the Open Web Application Security Project's (OWASP) list of top 10 Web vulnerabilities for more than a decade. Just this week, in fact, HackerOne published a report showing XSS errors to be by far the most common security vulnerability in Web apps across organizations. Both XSS and SQLi are well understood, and many researchers have catalogued the dangers associated with them for years.
The fact that so many Web apps still have them reflects the relatively scant attention paid to security in the application development stage, says Andy Ellis, chief security officer at Akamai. "It is not that the developers are making errors," he says. "It is system that we put them into that is dangerous."
[...] Akamai's data[pdf] shows most Web application attacks originate from inside the US and most targets are US-based as well. Of the nearly 4 billion application-layer attacks that Akamai counted over the 17-month period, some 2.7 billion targeted US organizations. Companies in the UK, Germany, Brazil, and India were also relatively heavily targeted. though nowhere nearly as much as US companies.
(Score: 2) by Common Joe on Sunday June 16 2019, @03:48AM (1 child)
This is what surprises me the most. For some home brew stuff, Years ago, I wrote some server facing stuff for PostgreSQL in a three tier system. A C# program I wrote analyzed that, and it wrote a C#-based interface to be included in the server code that completely shut down the SQL injection attack angle. (It wasn't good enough to release publicly. I would have if I'd had time.) I'm shocked that I've never seen something generic like what you or I have done in the wild.
What do you use to do that? Something home brew? Or is there something found in a place like GitHub that you use for that?
(Score: 2) by The Mighty Buzzard on Tuesday June 18 2019, @01:47PM
Have a look at the rehash source on github, it's supposed to be entirely like that except for a few places where user input doesn't exist.
My rights don't end where your fear begins.