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

Apache shouldn't be allowed to spawn shells #231

Closed
mstemm opened this issue Apr 6, 2017 · 0 comments · Fixed by #232
Closed

Apache shouldn't be allowed to spawn shells #231

mstemm opened this issue Apr 6, 2017 · 0 comments · Fixed by #232
Assignees

Comments

@mstemm
Copy link
Contributor

mstemm commented Apr 6, 2017

apache2 is currently on the list of programs that are allowed to spawn shells inside a container. However, when apache uses mod_{php,perl}, etc to directly evaluate interpreted code, this could mean that shells spawned by the interpreted php, perl, etc. scripts won't be detected.

The fix is to remove apache2 from the list. We'll fix any false positives that get re-introduced in a different way.

mstemm added a commit that referenced this issue Apr 6, 2017
This ensures that interpreted php,perl,etc code run by apache won't be
able to spawn shells, either.

This fixes #231.
@mstemm mstemm self-assigned this Apr 6, 2017
leogr pushed a commit to falcosecurity/rules that referenced this issue Dec 21, 2022
This ensures that interpreted php,perl,etc code run by apache won't be
able to spawn shells, either.

This fixes falcosecurity/falco#231.
leogr pushed a commit to falcosecurity/rules that referenced this issue Dec 21, 2022
This ensures that interpreted php,perl,etc code run by apache won't be
able to spawn shells, either.

This fixes falcosecurity/falco#231.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant