Saturday, January 26, 2008

Another bad day at the office

A software error during routine maintenance caused an ISP, Charter Communications, to delete the contents of 14,000 customer email accounts.

"Charter gives each new Internet user a free e-mail account, but some customers opt to use other accounts instead. So every three months the company deletes inactive accounts, Lamont said. "During this maintenance we erroneously deleted active accounts along with the others," Lamont said. "It's never happened before. They are taking steps to make sure it never happens again."


The news article doesn't mention whether the "software error" was an unfortunate and evidently untested change to the maintenance scripts (indicating a hole in their change management processes), a genuine bug in the code (possible I guess), or a simple human error by an operator/systems manager (seems entirely possible). Since the lost email accounts disappeared forever in a puff of logic, it seems the ISP had no backups of customer data - not just 'no recent backups' but 'no backups whatsoever' (a gaping hole as far as their customers are concerned but no doubt a legitimate money-saving measure from the ISPs perspective).

This incident cost the ISP $50 credits to the affected customers, presumably rather less than 14,000x$50 ($700k) as some will defect before using up all their credit. The reputational damage could be even costlier, although the truth is that such unfortunate incidents can and indeed occasionally do strike most organizations.

The Silicon Valley piece ends rather lamely with "Computer experts advise backing up all important e-mail.", implying in effect that customers are to blame for losing their emails. In some ways that is true (presumably any small businesses or power users will have been using local emaiil clients such as Outlook to download and read their emails and so should have local backup copies) but I would advise Charter Comms to look long and hard at its information security arrangements.

Labels: , , , ,

Links to this post:

Create a Link

Thursday, January 10, 2008

Having a bad day at the office?

An IT systems administrator, fearing that he was about to be laid off, planted a logic bomb in his employer's systems. He survived the round of redundancies but detonated the logic bomb anyway. Fortunately for all concerned, bugs in the code prevented it working properly. In court, he was found guilty, sentenced to 30 months' jail time and found liable for $81,200 in restitution.

This story touches on quite a number of security topics:
- He was a trusted insider who went bad
- Logic bombs are a form of malware
- His office/day-job gave him privileged access to the company's IT assets
- Weak change management process controls did not prevent the bomb being installed
- The logic bomb had one or more bugs in the program/script
- Nevertheless it sparked a security incident
- He was called to account for the damage
- There was legal and presumably corporate policy noncompliance
- The risk of recurrence presumably remains

All in all, a nice multi-purpose security awareness case study.

PS The official US DOJ press release about the conviction is dated "Dec 8 2008", an integrity failure to boot.

Labels: , , , , , , , , ,

Links to this post:

Create a Link

Saturday, December 22, 2007

A Christmas present for ordinary computer users

Peter Gregory has blogged a list of free security software that is sure to appeal to "ordinary" (as in non-geek) computer users.

The only significant omission that occurs to me is online software security patching. Peter blogged just a week ago about a free and urgent security patch for Skype, perhaps not a good example as he chastises Skype for not publicising the patch. Microsoft Update is probably better.

Personally, I use Secunia's PSI (Personal Software Inspector) to track and stay current with security patches for most of the software on my home system, not just the Microsoft stuff. It does a good job for me but may be too geeky for ordinary mortals. What do you think? Is there a more user friendly option you'd recommend?

Labels: , , , ,

Links to this post:

Create a Link

Saturday, October 20, 2007

Automated field gun kills 9

This tragic story speaks for itself. After the operators cleared a jam in a Swiss/German Oerlikon 35mm MK5 anti-aircraft twin-barrelled gun during a live-firing military exercise, the gun turned to the left and fired a rapid burst of ½kg cannon shells directly at adjacent guns in the line, killing 9 soldiers and injuring 14. At the time, the gun was supposedly on 'manual', locked on to a target 1.5 to 2km away. On 'manual', it should not have turned at all.

According to news reports, "Defence pundit Helmoed-Römer Heitman told the Weekend Argus that if 'the cause lay in computer error, the reason for the tragedy might never be found.'" If 'computer error' equates to bug, then I can only assume the software must be horrendously complex and opaque to be so resistant to analysis ... which it probably is if it combines target acquisition/identification, range finding, gun control, oh and safety.

The South African Department of Defence is under pressure to conduct an inquiry.

Don't the procurers of such automated weaponry specify mechanical safety interlocks capable of physically preventing the turret from turning beyond set azimuth (and perhaps elevation) limits?

Labels: ,

Links to this post:

Create a Link

Tuesday, April 03, 2007

Microsoft animated cursor fix

A bug in Windows' handling of animated cursor files is being actively exploited by The Dark Side. Those of us on the Light Side are advised to deploy an emergency patch just released by Microsoft ... or consider moving to an alternative, less bug-ridden operating system sharpish, assuming such a beast exists.

More network security resources

Labels: , ,

Links to this post:

Create a Link

Thursday, October 19, 2006

Oracle admits 100 critical security flaws

Oracle, which "leads in customer relationship management" according to its home page has released a shed-load of patches containing : 22 security fixes for Oracle Database; 6 security fixes for Oracle HTTP Server; 35 security fixes for Oracle Application Express; 14 security fixes for Oracle Application Server; 13 security fixes for Oracle E-Business Suite; 8 security fixes for Oracle PeopleSoft Enterprise PeopleTools and Enterprise Portal Solutions; 1 security fix for JD Edwards EnterpriseOne; 1 security fix for Oracle Pharmaceutical Applications; and a partridge in a pear tree. If you run Oracle software, get busy with the patching to miminize the risk of incidents. If you work for Oracle, how about some of that customer relationship management i.e. better quality software for your valued customers?
More links on incident management and bugs!

Labels: , ,

Links to this post:

Create a Link

Friday, October 13, 2006

Patch within 15 mins

Microsoft has dumped another bucket of patches on its customers. Read the Microsoft info page or, for another perspective, check out what SANS Internet Storm Center has to say. The ISC picks out three critical patches, one of which they rate "PATCH NOW" since it is being actively exploited. If you are too busy to check, test or download the patches, remember that the clock is ticking. A few days back, the BBC reported that a honeypot system running unpatched XP Home gets compromised within ~15 minutes of web connection. Get your patching processes up to scratch or face trying to explain to your stakeholders why you suffered avoidable information security incidents ...
More incident management and bugs! resources

Labels: , ,

Links to this post:

Create a Link

Friday, September 29, 2006

PowerPoint zero-day

Hot on the heels of the VML bug in Microsoft Internet Explorer comes news of yet another zero-day Microsoft exploit affecting PowerPoint. Gosh.
More incident management links

Labels: ,

Links to this post:

Create a Link

Thursday, September 28, 2006

Being born yesterday

Hackers are so desperate to exploit vulnerabilities such as the VML bug, they are becoming quite incoherent in their excitement. Here's the text of an email I just received:

Mail server report.

Our firewall determined the e-mails containing worm copies are being sent from your computer.

Nowadays it happens from many computers, because this is a new virus type (Network Worms).


Using the new bug in the Windows, these viruses infect the computer unnoticeably.
After the penetrating into the computer the virus harvests all the e-mail addresses and sends the copies of itself to these e-mail
addresses

Please install updates for worm elimination and your computer restoring.

Best regards,
Customers support service


Needless to say, I didn't open the attachment (which had already been quarantined by the antivirus software, in any case). Phew, that was a close one!
More Bugs! and malware links

Labels: , , , ,

Links to this post:

Create a Link

VML exploit awareness video

If you've been following the information security headlines over the past week or so, you will have heard about a nasty zero-day Microsoft exploit in the wild - or rather three exploits in fact, all targeting a buffer overflow in Internet Explorer's handling of Vector Markup Language.
Watchguard's excellent VML exploit video demonstrating the attack is an object lesson in technical awareness presentations - professionally produced, clear and straightforward, and just over 4 minutes long. Nice. Microsoft issued an emergency patch for the bug this week. Meanwhile, SANS and MessageLabs are reporting that malicious eCards are in circulation, exploiting unpatched vulnerable systems.
More links on bugs!

Labels: ,

Links to this post:

Create a Link

Tuesday, September 05, 2006

Bugging you

And now for something completely different.
More links on bugs! and other portable security issues

Labels: ,

Links to this post:

Create a Link

Saturday, August 26, 2006

Addressing risks in legacy IT systems


The diagram comes from an excellent new white paper by Israeli security specialist, Danny Lieberman. It eloquently describes a systematic approach for assessing and addressing risks in legacy systems. It examines the question of why there are so many bugs (including defects that cause security issues) in software, and goes on to explain the derivation of threat models (using the Practical Threat Analysis tool) to design appropriate controls.
More risk management, secure development and Bugs! links

Labels: , ,

Links to this post:

Create a Link

Saturday, June 10, 2006

M$ kills more bugs

Microsoft's Security Program Manager Chris Budd explains Ten Principles of Microsoft Patch Management. Chris clearly knows what he is talking about because Microsoft is highly experienced at releasing patches for its software. The Technet article guides Microsoft's valued customers in how to design and implement efficient processes for sticking plasters over the cracks caused by the vendor's quality control failures. Why do we still put up with this nonsense? What's worse, why do we continually pay for it? [Sorry, I'm feeling particularly cynical today and getting rather tired of battling the legion of bugs.]

More resources on bugs!

Labels:

Links to this post:

Create a Link

Saturday, May 20, 2006

Microsoft's Security Development Lifecycle

Microsoft’s Trustworthy Computing Initiative involved retraining loads of developers to code with security in mind. Whilst Microsoft's secure development methods generally follow the traditional waterfall approach, take a closer look at the activities immediately preceding release. “During the release phase, the software should be subject to a Final Security Review (‘FSR’). The goal of the FSR is to answer one question. ‘From a security viewpoint, is this software ready to deliver to customers?’ The FSR is conducted two to six months prior to software completion, depending on the scope of the software. The software must be in a stable state before the FSR, with only minimal non-security changes expected prior to release.” In your organization, does independent security testing occur 2 to 6 months before release?! Of course, even this method is not absolutely perfect: at least one buffer overflow vulnerability in Word somehow slipped through the net.

More security-development integration resources

Labels: ,

Links to this post:

Create a Link

Friday, February 24, 2006

Building secure systems

A DHS/CERT/CEI website BuildSecurityIn promotes secure coding practices. The site has a couple of dozen white papers already and will hopefully become a useful source of advice for developers and project managers interested in developing secure code.

More resources on Bugs!

Labels:

Links to this post:

Create a Link

Friday, February 10, 2006

Yet more Microsoft bugs

Following on from the .WMF Windows Meta File zero-day exploit story at the end of 2005, Network World reports that Microsoft has acknowledged another bug in the .WMF code, plus another unconnected bug, and independent researchers have identified a third. The truth is that software bugs are discovered and fixed all the time - this is presumably only newsworthy because of the connection to .WMF and because all three bugs have security implications.
Microsoft has also published advance details of the clutch of bugs to be patched next Patch Tuesday.
More resources on Bugs!

Labels: ,

Links to this post:

Create a Link

Wednesday, February 08, 2006

Russian hackers hawked Windows exploit for $4k

News.com reports that Russian hackers were selling code exploiting the .WMF Windows Meta File bug at the end of 2005. For $4,000 a time, allegedly, one could purchase the zero-day exploit code.
More resources on Bugs!

Labels:

Links to this post:

Create a Link

Thursday, February 02, 2006

Firefox fixes funnies

A new release of Firefox fixes a number of bugs including "other security holes not yet disclosed". The implication is: update your Firefox before (more) black hats figure out what the holes are, and before the vendor discloses the nitty gritty details to help other black hats work out the flaws.

More Bugs! resources

Labels:

Links to this post:

Create a Link

Sunday, January 29, 2006

Cisco backdoor

A backdoor in a mainstream security product could certainly be considered a bug. The product is Cisco Security Monitoring, Analysis and Response System (CS-MARS) (CS-MARS) up to version 4.1.2 and the backdoor is an undocumented user ID with a default password giving access to the root fully-privileged administrator ID. Doh! The access was deliberately inserted allegedly for “advanced debugging purposes” - fair enough maybe but why on Earth did it end up in shipped code, and in a security product at that?!
More links on Bugs!

Labels: ,

Links to this post:

Create a Link

Thursday, August 04, 2005

Fix costs escalate 200x post implementation

It has been estimated that it is about 200 times more expensive to fix a problem when an IT system is in Production compared to fixing at the requirements analysis step during Development. The factor falls to about 4 for small IT projects but can exceed 500 for very large projects. Even if these figures are only vaguely close to the truth, the implications for quality assurance processes in IT development are crystal clear, as are the benefits of splitting massive projects into discrete sub-projects.

More change management, bugs and secure systems development resources

Labels: , ,

Links to this post:

Create a Link