attrition: advisory errata archive vendor_fail news charlatan lazlo security_comp_fail going_postal rant box_of_shit movie_review book_review music_review contest buy_shit
twitter: technical_difficulties unsolicited_updates foursquare wefollow musings imdb dmfail
hobbies: critter_of_the_day squirrel guinea_pig stalking
related: osf datalossdb conference osvdb
type: quote screenshot photo video tweet audio question chat link
Some discounts, you just can’t pass up.
Spammer let’s you unsubscribe, or not. SQLi instead maybe.
LIGATT Security did not get hacked! National Cyber Security is not run by LIGATT! It is not on any of LIGATT’s servers. It is run by the founder of the company and his networks. LIGATT does not get hack, we do the hacking!
@DisK0nn3cT: @attritionorg hacks gregory evans bio page #ligatt http://twitpic.com/1z25qj
@attritionorg: uh, the hell we did. someone unaffiliated with us tampered with the page, and is using a frame to load our content
Has anyone figured out where this is from?
Wonder why Twitter blocked access to this recently..
There’s a joke or three here somewhere.
This pattern demonstrates that LIGATT has no regard for their own security, and likely does not have the technical proficiency to properly defend their web sites from XSS attacks. Since many of their services are based on customer accounts, XSS is particularly important to the sites as authentication credentials would be at risk from a serious XSS attack.
Earlier today, on June 7, yet another XSS vulnerability was found in ligattsecurity.com. The initial tweet demonstrated the standard popup, and subsequent tweets demonstrated the injection of third-party content into LIGATT’s web site. The question remains, how can LIGATT promise to offer any level of security when they can’t protect their own sites from the most basic of XSS attacks over 22 days?
The administration/management login script on nationalcybersecurity.com is vulnerable to reflected cross site scripting. The affected (GET) URL parameter is “username.”
The site search script on nationalcybersecurity.com is vulnerable to reflected cross site scripting. The affected (GET) URL parameter is “Query.”
PayPal fail. Did my transaction go through or not…
Hertz unsubscribe failure. Way to handle no javascript. Virtual douchebags.
Well, this is awkward…
Symantec’s twitter feed seems to be having issues. (Following vs Followers)