Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Threat Intelligence

7/31/2018
03:50 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Hundreds of Registry Keys Exposed to Microsoft COM Hijacking

Experts believe there could be thousands more in the wild.

Microsoft Component Object Model (COM) hijacking is an old type of cyberattack getting a new spin as attackers find stealthy ways to maintain persistence and evade detection.

The Microsoft COM is a system integrated into Windows to facilitate interaction between software components through the operating system. COM is managed in the Windows registry, which contains keys that reference Phantom COM objects. These objects could refer to files that no longer exist on the hard drive and include old applications or obsolete programs.

Even if files are gone, registry keys will continue to refer to them. If an attacker hijacks a phantom COM object ID of a trusted application and instead uses it for a malicious file, he can load and execute the file onto the OS. So long as the COM object ID (CLSID) has been registered as a legitimate object, the malicious file will appear legitimate and bypass security tools.

Security tools often miss COM hijacking because hundreds of CLSIDs are available and are all connected to common Windows processes, such as explorer.exe, chrome.exe, svchost, and iexplore. New ones appear each day, making it tough for systems to keep up.

COM hijacking is now gaining popularity as attackers seek new ways to maintain persistence without autorun entries, which are easy to map, explains Cyberbit research director Meir Brown, in a new report on the attack vector. Researchers found hundreds of registry keys are vulnerable to COM hijacking, far more than was first believed.

"We knew COM hijacking was used for persistence and have seen some of this used for injection, but didn't know the scale of this phenomenon – how many entries there are in the registry which are vulnerable to COM hijacking," Meir explains. The tactic is commonly referred to as a persistence mechanism, but it's also one of the most effective ways to achieve stealth.

Hunting Registry Keys Online
Researchers ran a proof-of-concept experiment in which they put themselves in the attackers' shoes and sought out Phantom COM objects to take over. They mapped registry keys that failed to find and load a file, and tried to use those keys to load a fake dynamic link library (DLL).

The trial was a "troubling" success, says Brown, as researchers were able to load and run their DLL within the context of valid applications. The Windows machine loaded all of their objects without any side effects.

As they hunted for keys online, researchers found multiple samples using these keys in the wild. Hundreds of keys are vulnerable to COM hijacking and Phantom COM objects loading, they concluded. The process is easy for attackers to implement and doesn't require them to leverage code injection, a technique more frequently picked up by detection platforms.

COM hijacking is considered dangerous because it runs using legitimate user privileges, doesn't require reboot, and does reveal suspicious activity to the target, Meir says. It's gaining popularity; organizations should be aware and monitor the registry.

Researchers believe the scope of this issue goes far beyond the hundreds of potential vulnerabilities they found and could potentially reach into the thousands. Further, while COM hijacking is used in the wild, it remains less common than registry run key and injection tactics.

Related Content:

 

 

 

Black Hat USA returns to Las Vegas with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions and service providers in the Business Hall. Click for information on the conference and to register.

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
seanmajece
50%
50%
seanmajece,
User Rank: Apprentice
8/2/2018 | 5:44:48 AM
My opinion
In my opinion, it will be better for users to use IOS these adys.
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...