Skip to content

Consider blacklisting setuid binaries #2

Description

@madsmtm

We currently allow read+execute access to all binaries in $PATH to make things actually usable, but there might be security issues with allowing executing setuid binaries like sudo?

Will need to look into that, if it's a problem then a possible solution could be to iterate over all binaries in $PATH, and if the binary is a setuid binary, blacklist it? Though we'd have to make sure that the path iteration is the same as whatever is done in the sandbox itself, so maybe it'd be better to explicitly whitelist each non-setuid binary?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions