Cloud

12/12/2017
03:48 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Microsoft Azure AD Connect Flaw Elevates Employee Privilege

An improper default configuration gives employees unnecessary administrative privilege without their knowledge, making them ideal targets for hackers.

Microsoft today issued a security advisory to alert users to an improper default configuration in Azure AD Connect, which increases the number of "stealthy admins" on corporate networks and makes businesses more vulnerable to targeted attacks.

The flaw - which was discovered by Preempt researchers during a customer network review - was a separate advisory from Microsoft's monthly Patch Tuesday updates, also issued today. Microsoft released 34 security fixes in its December batch of security updates, which affect Windows, Office, Office Services and Web Apps, Exchange Server, Microsoft Malware Protection Engine, Internet Explorer, Edge, and ChakraCore. 

Microsoft's advisory for Azure AD Connect was published for an unpatchable issue related to the security configuration settings for the Active Directory Domain Services (AD DS) account used by Azure AD Connect when syncing to a directory. Default settings often give non-administrative employees permissions they don't need.

Preempt researchers found many employees on their customers' networks had some type of unnecessary administrative privilege, which came from unintentional inclusion in a protected administrative group. Active Directory audit systems often miss "stealthy admins," or admins who have higher domain privileges as a direct result of domain discretionary access control list (DACL) configuration.

"Usually, stealthy admins are created by accident," explains Preempt researcher Yaron Ziner. Employees are granted certain access for a legitimate purpose; for example, if a software requires particular privileges to install or if someone is in charge of resetting passwords.

Several permissions could give stealthy admins full domain admin privileges. Stealthy admins may be non-administrative users who can add users to security groups, which would enable them to make themselves a domain admin at any point. Another is the ability to replicate a domain, which includes the ability to read password hashes from the domain controller.

"The more privilege an account has, the higher the risk and easier the attacker's job is going to be," says Preempt cofounder and CEO Ajit Sancheti. Stealthy admin accounts are often less monitored than full domain admins despite their level of privilege. If an attacker gains access, they can determine the level of privilege and use it to their advantage.

Digging further into the issue, the researchers learned businesses were prone to having more stealthy admins when they installed Microsoft Office 365 with Azure AD Connect in on-premise environments, and used Azure AD Connect to connect between on-premise and the cloud.

More than 50% of Preempt clients were affected by a flaw in MSOL Azure AD Connect service account when installed with Express settings. Azure password sync, which is used to sync passwords between on-prem networks and cloud services, requires domain replication permissions.

"When you provision Office 365 in the organization, the first thing you need to do is sync the on-prem directory with the cloud directory," says Ziner. When Azure AD Connect is installed, it creates a service (MSOL) account that syncs directories to read on-prem passwords. This is a "stealthy admin" account: it can access passwords but doesn't have strong security measures.

Further, this account would not have AdminSDHolder protection, meaning other non-privileged users can reset its password and gain access. In many networks, the researchers report, the service account was a primary attack path for attackers with Account Operator permissions to increase their privilege and become full domain administrators. 

Consider a scenario in which a help desk employee has permission to reset non-admin passwords but lacks admin privileges. Because the MSOL account is part of the Built-in Users container, and the help desk team has permissions to reset passwords for that container, the help desk employee has full access to domain passwords and other higher privileges.

The discovery of MSOL as a stealthy administrator is "just one instance of a stealthy account that can lead to domain compromise," says Sancheti.

Businesses can protect themselves from the threat by first reviewing the stealthy admins in their network. Once you know who the stealthy admins are, determine whether additional permissions are necessary. If not, they should be removed.

Microsoft's Security Advisory 4056318 advises admins to avoid using the Account operators group since by default, members of this group have reset password permissions to objects under the User container. 

The company also recommends moving the AD DS account used by Azure AD Connect, and other privileged accounts, into an Organization Unit that is only accessible by highly trusted admins. When giving reset password permissions to specific users, limit their access to only user objects they are supposed to manage.

Related Content:

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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
'Hidden Tunnels' Help Hackers Launch Financial Services Attacks
Kelly Sheridan, Staff Editor, Dark Reading,  6/20/2018
Inside a SamSam Ransomware Attack
Ajit Sancheti, CEO and Co-Founder, Preempt,  6/20/2018
Tesla Employee Steals, Sabotages Company Data
Jai Vijayan, Freelance writer,  6/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-12716
PUBLISHED: 2018-06-25
The API service on Google Home and Chromecast devices before mid-July 2018 does not prevent DNS rebinding attacks from reading the scan_results JSON data, which allows remote attackers to determine the physical location of most web browsers by leveraging the presence of one of these devices on its l...
CVE-2018-12705
PUBLISHED: 2018-06-24
DIGISOL DG-BR4000NG devices have XSS via the SSID (it is validated only on the client side).
CVE-2018-12706
PUBLISHED: 2018-06-24
DIGISOL DG-BR4000NG devices have a Buffer Overflow via a long Authorization HTTP header.
CVE-2018-12714
PUBLISHED: 2018-06-24
An issue was discovered in the Linux kernel through 4.17.2. The filter parsing in kernel/trace/trace_events_filter.c could be called with no filter, which is an N=0 case when it expected at least one line to have been read, thus making the N-1 index invalid. This allows attackers to cause a denial o...
CVE-2018-12713
PUBLISHED: 2018-06-24
GIMP through 2.10.2 makes g_get_tmp_dir calls to establish temporary filenames, which may result in a filename that already exists, as demonstrated by the gimp_write_and_read_file function in app/tests/test-xcf.c. This might be leveraged by attackers to overwrite files or read file content that was ...