this post was submitted on 20 Apr 2024
974 points (97.1% liked)

linuxmemes

20688 readers
1233 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
974
mv Windows Linux (discuss.tchncs.de)
submitted 4 months ago by [email protected] to c/[email protected]
106 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 4 months ago* (last edited 4 months ago) (1 children)

You need Administrative permissions for psexec. It uploads a file to the target computer's \admin$ share (just C:\Windows) and starts a service to execute it. Services run as SYSTEM so that's why you get those privileges.

(Hah, I forgot your message while typing mine and just copied you :)

Edit: fixed c$ to admin$

[–] [email protected] 3 points 4 months ago* (last edited 4 months ago) (1 children)

I found a blog post outlining exactly that. If you use it locally, it will install and start a service temporarily. That service runs as SYSTEM and invokes your command. To succeed, you need to be a local administrator.

If you try the same remote, it tries to access \\remote-server-ip\$admin and installs the service with that. To succeed your current account on your local machine must exist on the remote machine and must be an administrator there.

So in short: It only works, if you've already the privilege to do so and the tool itself is not (ab)using a privilege escalation or something like that. Any hacker and virus may do the very same and doesn't need psexec - it's just easier for them to use that tool.

[–] [email protected] 1 points 4 months ago* (last edited 4 months ago)

Thank you for clearing it up!

And regarding your assessment: Exactly!