Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Path traversal mitigation #51

Open
GhostofGoes opened this issue Oct 4, 2019 · 0 comments
Open

Path traversal mitigation #51

GhostofGoes opened this issue Oct 4, 2019 · 0 comments
Assignees
Labels
security General security issues/weaknesses. Please do NOT report vulnerabilities via Issues!

Comments

@GhostofGoes
Copy link
Owner

Presently, system binary paths are determined by reading the PATH environment variable. This is problematic from a security perspective, as it could potentially lead to code execution (symlinks, manipulation of PATH, etc.). One potential mitigation is to determine the locations of the executables required at startup without relying on PATH. This could be accomplished through system fingerprinting, e.g. "we know the current system is Ubuntu < 14 therefore check these paths".

This can be completed after the refactor is completed, as that'll make fingerprinting more reliable and provide a concise and deterministic (mostly) list of the executables (and paths) required.

@GhostofGoes GhostofGoes self-assigned this Oct 4, 2019
@GhostofGoes GhostofGoes added this to the Stable Release (1.0) milestone Oct 4, 2019
@GhostofGoes GhostofGoes added the security General security issues/weaknesses. Please do NOT report vulnerabilities via Issues! label Oct 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
security General security issues/weaknesses. Please do NOT report vulnerabilities via Issues!
Projects
None yet
Development

No branches or pull requests

1 participant