The company's managing director Ty Miller gave a presentation on the attack method at the recent Black Hat conference in Las Vegas, along with senior security consultant Paul Kalinin.
Miller said that there was no need to compromise passwords as the attack could be carried out with bog standard user accounts.
Asked if he had contacted Microsoft about his findings, Miller told iTWire that the Active Directory Botnet threat attack was not a vulnerability and as such a patch wasn't required. It was a flaw in how Active Directory was being implemented.
|
|
Due to the architecture of nearly every Active Directory implementation, almost all servers, workstations, laptops, mobile devices, and wireless devices in organisations can connect to a Domain Controller for authentication purposes.
"This provides the ability for our internal Active Directory Botnet to communicate through a network of strategically placed Active Directory C&C servers," he said.
The Active Directory Botnet attack technique revealed a fundamental flaw in the way almost every organisation implemented their Microsoft Windows Active Directory solution, he said, compromising their overall security and ability to contain security breaches.
Miller said standard Active Directory attributes and features forced the Domain Controllers to act as a central communications point for all internally compromised systems.
Detailing the way the attack was implemented, Miller said standard Active Directory accounts supported more than 50 user attributes that could be combined to create a communication channel between any compromised domain machine located in any part of an organisation.
"The Active Directory Botnet Client injects unique data entries into their corresponding Active Directory account attributes within the target Domain Controller, and begins polling to identify other compromised systems within the domain," Miller said.
"At this point, any Active Directory Botnet Client within the domain can identify compromised machines and begin issuing commands to be executed on either individual systems or across all infected endpoints."
He said if an organisation used the Azure Cloud Active Directory, then the Active Directory Botnet could use the synchronisation from an on-premise Active Directory to the cloud to create an egress channel.
This could be then used to extract data from the organisation through production Active Directory protocols.
Graphic: courtesy Microsoft.
