Confirmed users
717
edits
Security/ProcessIsolation/ThreatModel: Difference between revisions
Security/ProcessIsolation/ThreatModel (view source)
Revision as of 21:14, 17 June 2009
, 17 June 2009→General threats
| Line 117: | Line 117: | ||
- potentially registry and network access (binary sockets, etc) - or allow them unlimited access | - potentially registry and network access (binary sockets, etc) - or allow them unlimited access | ||
==General | ==General pitfalls== | ||
*Some Windows processes don't respect token privileges, they clone their own token based upon the user with default permissions (task manager is an example) | *Some Windows processes don't respect token privileges, they clone their own token based upon the user with default permissions (task manager is an example) | ||
*Some services allow anyone to talk to them regardless of restrictions (Telnet service for example) | *Some services allow anyone to talk to them regardless of restrictions (Telnet service for example) | ||
*There are a lot of DLLs in Windows that inject themselves into a process (like renderer) that can't deal with restricted rights tokens, so they crash or behave inappropriately (leave handles open, etc). | *There are a lot of DLLs in Windows that inject themselves into a process (like renderer) that can't deal with restricted rights tokens, so they crash or behave inappropriately (leave handles open, etc). | ||