Report: LulzSec Used SQL Injection, XSS and RFI

Status
Not open for further replies.
They disbanded because the government and companies were investigating them, NOT because they 50 days are up. I guess they think the public is suppose to believe them. They are cowards hiding behind a computer just like criminals who rob people wearing masks. People who agree on what they did needs to get their head checked!!!
 
Not a huge shock, as I've rarely seen anyone defend the skill set of these guys. And although I do not condone these attacks in the slightest, it does raise the question: Why have all companies not implemented and/or developed better solutions to XSS and SQL injection attacks?

You don't have to spend millions and millions of dollars to defend against SQL injection or XSS, they are very well established exploits and can easily be defended against or deterred. Plus it leaves traces, especially if the company has taken steps to make it harder to access SQL command injection. Fix the easy stuff that all crackers can easily exploit (like Lulzsec has) first, and then move on to the harder stuff meant for professional crackers.

All this talk about building an impenetrable fortress of internet security. It doesn't matter how many packet sniffers, IP loggers, firewalls, or intrusion detectors you have surrounding your fortress, if you don't have a good foundation (essential security fixes), then the fortress will collapse on itself. These guys didn't care about whether their hacks were quiet or not. They WANTED the publicity and that's what made these attacks so successful.

 
SQL Injection and XXS are so easy to prevent too. You don't need to be an intelligent programmer to prevent them, just use the latest standards (or even any standards made in the last 5 years or so) and they automatically prevent it. In asp.net you have to override specific settings to allow XXS and don't use dynamic SQL. It may be easier to write, but I have yet to see a case where you couldn't code around the need to use it.
 
who cares why they were disbanded? they proved, much like anon has, that simple attacks are still way to effective to bother with trying any revolutionary hacks.

We dont live in a world that allows people to leave there cars running while they go shopping. We live in a world that has crime, and lulzsec and anon have continually proven that if a major cyberwar happens, the US and major corporations have little defenses in place to defend against them.

 
[citation][nom]officeguy[/nom]They disbanded because the government and companies were investigating them, NOT because they 50 days are up. I guess they think the public is suppose to believe them. They are cowards hiding behind a computer just like criminals who rob people wearing masks. People who agree on what they did needs to get their head checked!!![/citation]

How's the view from up there?
 
That makes sense. Firewalls and such that are meant to keep people out are no good against these types of attacks, since they are using the same routes that normal application usage would use.
 
[citation][nom]gm0n3y[/nom]SQL Injection and XXS are so easy to prevent [/citation]

aaaaaaaaaaaaaaaaaaaaaaand the CIA got hacked too. This is sad.

 
So the phrase "Who's the bigger fool, the fool or the fool that follows" is the first thing I thought when reading this article. I see a lot of comments on Lulzsec about them being no skilled amateurs, using kiddie scripts and basic hacking tools. That may be true, but what's worse. No skill amateurs using old school type hacks or the companies/goverment that chose to ignore easily patchable loopholes into their systems and allow the hacks to suceed?
 
[citation][nom]gm0n3y[/nom]SQL Injection and XXS are so easy to prevent too. You don't need to be an intelligent programmer to prevent them, just use the latest standards (or even any standards made in the last 5 years or so) and they automatically prevent it. In asp.net you have to override specific settings to allow XXS and don't use dynamic SQL. It may be easier to write, but I have yet to see a case where you couldn't code around the need to use it.[/citation]

True you don't have to be a smart programmer to prevent these things. You just have to not be a lazy programmer. Lazy is the biggest problem in the US and Europe these days.
 
[citation][nom]the_krasno[/nom]aaaaaaaaaaaaaaaaaaaaaaand the CIA got hacked too. This is sad.[/citation]

CIA got DDoS'd, not hacked. Big difference.
 
[citation][nom]balister[/nom]CIA got DDoS'd, not hacked. Big difference.[/citation]
Keep in mind that this attack was against their public website not their internal computer network. The public website is a resource available to all and only hurts internet users that rely on the information for research etc.
 
revolutionary...why needs those methods when security companies refuse to fix the old problems....good on them for using old tech to destroy new tech
 
One big problem is the organization of larger IT shops themselves. Most companies have a network department and a development department. The mentality of the dev dept is to produce the product and depend on the network dept to protect them from nefarious activity. The role of the network dept is to keep the bad man out, so I can see where a corporate culture change is required.
 
Status
Not open for further replies.