r/PowerShell • u/Best_Yasuo_EUW • Aug 25 '22
Question Run Powershell as admin without admin rights
Hello everyone, does anyone know or has done this? I need to make Powershell to be able to be ran as admin without actually inputting any credentials from an account, that is not an administrator - a normal domain user to be able to open up elevated Powershell even though he has no rights.
I've tried a few things like giving Full Control to Powershell.exe in System32, but that didn't seem to work
I've tried creating this script this batch file:
@ ECHO OFF
SET ThisScriptsDirectory=C:\
SET PowerShellScriptPath=C:\PSADMIN.ps1
PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& {Start-Process PowerShell -
ArgumentList '-NoProfile -ExecutionPolicy Bypass -File ""C:\PSADMIN.ps1""' -Verb RunAs}";
Which goes to a ps1 file with "Start-Process Powershell"
And run this in task scheduler as a domain admin user with highest privileges, which actually does run OK on my computer in which I'm admin in, but not for a user that is not an admin user (it does say script was ran when it was done by a user but it does not work, but when You run the batch file by hand it does work - strange.)
Is it even possible to do some domain ACLs to let specific users to open up specific programs as an admin?
Thanks a lot
EDIT: From what I can see from replies, this looks like a pretty bad idea, and I couldn't agree more. So I've got an idea to install Hyper-V for people that need to test things with admin rights.
Still not sure what to do with specific programs that need to be ran as admin on a work computer
EDIT 2: Thanks everyone for their insights, I probably should be deleting this thread, as this doesn't seem like a good idea at all, but that's why I'm consulting specialists here, if someone else clueless comes here, he should see this thread. Thanks for solution You were giving. This was quite a broad learning experience which I love. Have a great day.
9
1
u/Best_Yasuo_EUW Aug 25 '22
I mean, all of the comments are right and I know this as well (and for gods sake, stop with being aggressive, thanks for the tips, solutions and heads-ups). Everything is still in testing and nothing is live yet and will not go live without a lot of permissions, it's just a request from a company and my manager. Thanks a lot for clearing it all up, people.
4
u/purplemonkeymad Aug 25 '22
What are you expecting people to do with this admin prompt? You would probably be better off updating ACLs of the things that need changes to allow users to change them*.
*There are security considerations you will have to make for each item.
4
3
u/OptimoP Aug 25 '22
To answer this question.. I don't think you can do this the way you need. I don't know how to give Domain Admin rights to a user or machine without adding the account directly to the Domain Admins group.
Depending on what your needs are, can you set up a terminal that does ONLY what is needed and air-gapped from everything else? Can you set up a scheduled task on the server (I assume) to provide the report/or service at regular intervals?
2
u/C0gn171v3D1550n4nc3 Aug 25 '22
If you wanna be sketchy AF, though I wouldn't recommend it. you could put admin username and password in an array inside a bat or ps1 file that opens powershell.exe. This would allow a non priv user to simply run it and have admin. MASSIVE SECURITY RISK THOUGH. The array won't provide more than basic obfuscation, so your admin cred are pretty much just sitting there.
1
u/lerun Aug 25 '22
Only need to be LOCAL admin on the box the PS script is running to be able to open up elevated.
1
1
1
1
u/mjohonson20 Aug 25 '22
Get a PAM solution. Delinea formerly Thycotics allows you elevate the app and not the user. And I think licensing is per agent/device so it should be affordable.
1
u/Narabug Aug 26 '22
The direct answer to your question lies within a toolkit named PowerSploit, and involves token manipulation. You basically have to make an admin token and hand it to the non-admin user or process. For what it’s worth, any security tool will immediately flag PowerSploit libraries and delete or quarantine them.
There are also apps/tools that can similarly accomplish this. For example, you could have a program in SCCM that simply launches an interactive command prompt - by default it will launch as the system account.
Programs I know if are MakeMeAdmin and BeyondTrust Privilege Management for Windows.
As others are saying, you have to be careful with what you allow people to run as admin. Command prompts are a pretty large no no.
1
u/TheOnlyBliebervik Dec 29 '23
If you become an admin, you can make a new administrator account, which you can then use to make your original account an admin account
1
u/jimb2 Aug 26 '22
This would be a serious security failure. This means that any partially compromised user gets the keys to the kingdom. Be careful what you wish for.
1
1
u/Maximum_Ad_9965 Jan 10 '23
You can setup a GPO to run scriptunder a user or computer context with admin rights. It´s not possible to click "run as administrator" on any .link or binary without admin rights.
1
u/myrland Aug 25 '22
Creating a scheduled task that runs under the SYSTEM context and executes a specific Powershell file should work, but it's not exactly secure in any way whatsoever.
Please don't ever go this route with any sensitive credentials like domain admin.
1
u/johnjones_24210 Aug 25 '22
Stop f*ing guessing with desperation moves like giving Full Control.
Hope you have proven backups
-5
u/Best_Yasuo_EUW Aug 25 '22
For people saying that running powershell with domain admin credentials instead of local admin credentials, is that really a problem? It is opening in elevated state either way, is there any difference?
5
u/yoyoyoitsyaboiii Aug 25 '22
You should never use highly privileged credentials like domain admin on a user workstation unless you want to get your entire domain hacked.
1
1
u/StConvolute Aug 25 '22
Fun fact (maybe?), the pass the hash technique was developed in 1997...
Also, most freshly deployed domains default to allow NTLMv1 for all connections. No password salting, super low cipher strength.
Anyway, in summary. I agree.
1
u/lerun Aug 25 '22
Yes, there is a big difference from being able to change everything in AD and all devices connected to it, to only change things on that one box.
Powershell is a powerfull tool and can do anything on windows it has access to. So always give the least amount of access for the task it is needed for.
1
u/BlackV Aug 25 '22
yes, it is a problem, those creds are now cached on that local machine, any malware/l337 haxor/etc now has a change to steal those creds
1
Aug 25 '22
Mate I'm sorry to say this but if you can't tell the difference between local admin and domain admin then you really need intense training. Try the MD 100 or MD 101.
29
u/MNmetalhead Aug 25 '22
So, “how do I bypass device security?”
If the user has a business need for elevated rights, then they should have an account with those rights. If they don’t have a business need, they don’t get those rights. Basic RBAC.
Why does the user need elevated rights for PowerShell? That’s extremely dangerous to the device and the organization.