Cannot find process with ID for UDP Endpoints about privesccheck HOT 2 CLOSED

Problem fixed, I simply added -ErrorAction SilentlyContinue to ignore errors in case the process associated to the TCP/UDP endpoint no longer exists.

Get-Process -PID $ProcessId -ErrorAction SilentlyContinue

from privesccheck.

Hello,

Thank you for reporting this issue.

I doubt this is a matter of privileges as Get-Process can be invoked even on protected processes for instance. A race condition between the time the ports are enumerated and the time the process is queried is possible but unlikely, especially as you are able to reproduce the issue reliably.

The behavior you are observing could be caused by a forking mechanism. The process that created the socket no longer exists, I don't know.

Whatever the reason, you are right, the script is missing some error handling. I will see how I can fix this.

Thanks again! :)

from privesccheck.