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

fix(permissions): disallow launching subprocess with LD_PRELOAD env var without full run permissions #25221

Merged

Conversation

dsherret
Copy link
Member

Ref #25215

Closes #11964

Copy link
Member

@bartlomieju bartlomieju left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM to me too, users relying on LD_PRELOAD will most likely rely on addition isolation layers like docker, and those who don't will benefit from this change.

@bartlomieju bartlomieju added this to the 2.0.0-rc.0 milestone Aug 28, 2024
@bartlomieju bartlomieju added the backport:1.46 This PR needs to be backported to v1.46 branch label Aug 28, 2024
@dsherret dsherret merged commit 1a6fd38 into denoland:main Aug 28, 2024
17 checks passed
@dsherret dsherret deleted the fix_disallow_launching_subprocess_ld_preload branch August 28, 2024 02:03
dsherret added a commit that referenced this pull request Aug 29, 2024
…out full --allow-run permissions (#25271)

Follow up to #25221

I looked into what the list was and it was quite extensive, so I think
as suggested in
#11964 (comment) we
should disallow this for any `LD_` prefixed env var.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:1.46 This PR needs to be backported to v1.46 branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Permission to run specific command + permission to write somewhere = permission to run anything
3 participants