Feeds

MS explains 7-year patch delay

Legacy networking problem cure as bad as disease

3 Big data security analytics techniques

Microsoft has explained why it took seven years to patch a known vulnerability. Fixing the bug earlier would have taken out network applications and potential exploits alike, it explained.

Security bulletin MS08-068 fixed a flaw in the SMB (Server Message Block) component of Windows, first demonstrated by Sir Dystic of Cult of the Dead Cow fame at a hacking conference in 2001, if not before. The flaw opened the door to SMB replay or reflection attacks that would have allowed the operator of a malicious SMB server to run exploits on vulnerable PCs.

The flaw was rated as important by Microsoft but critical by some independent security watchers, such as the SANS Institute's Internet Storm Centre.

Microsoft explained the delay on issuing a patch on the effect a fix would have had on network-based applications. In a post on Microsoft's Security Response Blog, Christopher Budd explains that the SMBRElay attack worked in much the same way as its legacy NTLM protocol.

"When this issue was first raised back in 2001, we said that we could not make changes to address this issue without negatively impacting network-based applications. And to be clear, the impact would have been to render many (or nearly all) customers’ network-based applications then inoperable," Budd explained.

Interaction between programs, for example Outlook 2000 and Exchange 2000, would have been affected by a patch at the time, according to Budd. Redmond advised customers to apply a workaround - involving SMB signing - but always knew this approach had its limitations.

"We did say that customers who were concerned about this issue could use SMB signing as an effective mitigation, but, the reality was that there were similar constraints that made it infeasible for customers to implement SMB signing," Budd added.

Gradual changes Microsoft has introduced with successive versions of its software have reduced the scope of the flaw and allowing Redmond to (finally) issue a patch last Tuesday.

Security vendors criticised Microsoft for its delay in developing a patch, a failure which left customers open to attack. "Microsoft has known of this problem since 2001 and was not able to (or chose not to) fix it until now. This also means that working exploit code has been available for all Operating Systems including Windows NT 4, Windows 2000, XP, Windows Server 2003, Vista and Windows 2008. However, as Microsoft correctly states, exploitation is severely mitigated on Vista and Windows 2008," Eric Schultze, CTO at security tool firm Shavlik notes.

Tests for the vulnerability have been included with the Metasploit security tool since July 2007. Its developers are critical of Microsoft's long-waited update. "The MS08-068 patch addresses this attack only in the case where the attacker connects back to the victim ... The patch does NOT address the case where the attacker relays the connection to a third-party host that the victim has access to," Metasploit said. ®

3 Big data security analytics techniques

More from The Register

next story
Obama allows NSA to exploit 0-days: report
If the spooks say they need it, they get it
Samsung Galaxy S5 fingerprint scanner hacked in just 4 DAYS
Sammy's newbie cooked slower than iPhone, also costs more to build
Putin tells Snowden: Russia conducts no US-style mass surveillance
Gov't is too broke for that, Russian prez says
Snowden-inspired crypto-email service Lavaboom launches
German service pays tribute to Lavabit
Mounties always get their man: Heartbleed 'hacker', 19, CUFFED
Canadian teen accused of raiding tax computers using OpenSSL bug
One year on: diplomatic fail as Chinese APT gangs get back to work
Mandiant says past 12 months shows Beijing won't call off its hackers
Call of Duty 'fragged using OpenSSL's Heartbleed exploit'
So it begins ... or maybe not, says one analyst
Heartbleed exploit, inoculation, both released
File under 'this is going to hurt you more than it hurts me'
prev story

Whitepapers

Securing web applications made simple and scalable
In this whitepaper learn how automated security testing can provide a simple and scalable way to protect your web applications.
3 Big data security analytics techniques
Applying these Big Data security analytics techniques can help you make your business safer by detecting attacks early, before significant damage is done.
The benefits of software based PBX
Why you should break free from your proprietary PBX and how to leverage your existing server hardware.
Top three mobile application threats
Learn about three of the top mobile application security threats facing businesses today and recommendations on how to mitigate the risk.
Combat fraud and increase customer satisfaction
Based on their experience using HP ArcSight Enterprise Security Manager for IT security operations, Finansbank moved to HP ArcSight ESM for fraud management.