Feeds

Meet the future of Windows security exploits

Application logic corruption

  • alert
  • submit to reddit

Internet Security Threat Report 2014

Black Hat Europe Buffer overflow bugs, for years the most prevalent type of security vulnerability, will become a thing of the past as crackers realise the potential of different ways to exploiting Windows machines.

Sloppy programming practices (the root cause of buffer overflow vulnerabilities) give rise to security bugs where arbitrary and malicious code can be injected into a system, through a carefully crafted malformed data entry.

Generally, this spurious input is much longer than a program expects, causing code to overflow the buffer and enter parts of a system where it may be subsequently executed. The technique has been successful used against both Unix and NT machines on numerous occasions.

Halvar Flake, "Reverse Engineer" at Black Hat Consulting, said such standard stack-smashing overflows are getting rarer in well-audited code, so crackers will turn to fresh ways of executing arbitrary code.

During a well received presentation at last week's Black Hat conference in Amsterdam, Flake showed how heap overflow attacks could be used to write more or less arbitrary data to more or less arbitrary locations. He described these as Third Generation Exploits on NT/Win2k Platforms, something explained in greater detail here, and although he told us it's a term he invented himself, we're happy to go along with it since we liked the cut of his jib.

Such third generation exploits mean it is possible to subvert the logic of a Windows app by modifying its variables.

He also outlined future cracker strategies involving creating a large number of threads in a multithreaded environment, which make an exploit "80-90 per cent reliable and independent of NT/Win2000/XP version, service pack and hot fix".

Heap overflow exploits (such as format string bugs and particularly malloc()/free()-manipulations) give attackers two powerful techniques.

Such tactics have been used, and documented, on *nix platforms and the value of Flake's work is to highlight the risk of the exploitation of the technique on NT/Win2k boxes. ®

Related Stories

Win XP slays buffer overflow bugs
MS 'Security Framework' is another .NET vulnerability
MS says stop discussing hack exploits
Buffer the FTP Slayer
Redhat worm touts instant noodles
FBI lists 20 most dangerous Internet security holes
FBI warns as Unix server flaw gets automated

Secure remote control for conventional and virtual desktops

More from The Register

next story
Knock Knock tool makes a joke of Mac AV
Yes, we know Macs 'don't get viruses', but when they do this code'll spot 'em
Feds seek potential 'second Snowden' gov doc leaker – report
Hang on, Ed wasn't here when we compiled THIS document
Why weasel words might not work for Whisper
CEO suspends editor but privacy questions remain
DEATH by PowerPoint: Microsoft warns of 0-day attack hidden in slides
Might put out patch in update, might chuck it out sooner
BlackEnergy crimeware coursing through US control systems
US CERT says three flavours of control kit are under attack
prev story

Whitepapers

Why cloud backup?
Combining the latest advancements in disk-based backup with secure, integrated, cloud technologies offer organizations fast and assured recovery of their critical enterprise data.
Forging a new future with identity relationship management
Learn about ForgeRock's next generation IRM platform and how it is designed to empower CEOS's and enterprises to engage with consumers.
High Performance for All
While HPC is not new, it has traditionally been seen as a specialist area – is it now geared up to meet more mainstream requirements?
New hybrid storage solutions
Tackling data challenges through emerging hybrid storage solutions that enable optimum database performance whilst managing costs and increasingly large data stores.
Getting ahead of the compliance curve
Learn about new services that make it easy to discover and manage certificates across the enterprise and how to get ahead of the compliance curve.