Updated Microsoft's PowerShell feature “Just Enough Administration” (JEA) is, apparently, “way too much administration” according to researcher Matt Weeks.

In this write-up of JEA, root9B and Metasploit module developer Weeks says JEA profiles aren't much of a barrier, since people with JEA profiles can escalate themselves to sysadmin status. Cutting to the conclusion:

“Every JEA profile I had found Microsoft has published can be bypassed to obtain complete system administrative rights, most of them immediately, reliably, and without requiring any special configuration.”

The idea with JEA is to provide granular administrative profile management – a good thing, if only it worked out that way.

By way of demonstration, Weeks provides a variety of examples in which capabilities in JEA are exploitable.

The Add-Computer “cmdlet”, used to add a computer to a domain or change its domain, and which Weeks says is “a reliable vector to break the JEA security barrier, and escalate privileges to complete unrestricted system control”.

His attack doesn't use any hacks-or-cracks stuff: it ends with the new computer pulling group policy from an attacker-controlled Domain Controller providing group policy settings.

Result? Success: the victim machine “will pull group policy settings from your new server, enabling you via a group policy configuration to change any setting, drop the firewall, execute any command as system via startup scripts or scheduled tasks, or directly log in as the domain admin. You have broken the 'security barrier' and have full unrestricted administrative control over the system.”

There are slips in the Microsoft-provided JEA General Profile, so an attacker can launch the New-Service cmdlet (any command is launched with SYSTEM rights); Get-WinEvent and Get-EventLog, while giving admins access to event logs also are “a critical vulnerability”, by revealing admin account passwords.

There are also vulnerabilities in the JEA Web server admin profiles, he claims.

Weeks says Microsoft has promised to update its JEA documentation, making it clear that people with JEA profiles should be managed as closely as anybody else with administrative access.

Weeks' previous work includes creating a Metasploit module that attacked the favourite software of “your computer has been hacked” phone scammers. ®

Update: Matt Weeks has contacted The Register to make a couple of points.

First, he noted: "It's worth mentioning that JEA can be a real security barrier, it's just difficult to do so securely in a useful way, since common admin cmdlets tend to have all kinds of hidden implications. I did not break every JEA role capability, just the provided examples."

He also asked us to note that "what I was calling JEA profiles are properly called JEA role capabilities", which we're more than happy to do. ®