mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #4780] private-cwd leaks access to the entire filesystem #2778
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#2778
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @WhyNotHugo on GitHub (Dec 16, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4780
Description
Using
firejail --private --private-cwd=. /usr/bin/shleaks access to the entire filesystem.Steps to Reproduce
cdinto some subdirectory of$HOME.ls ../../some-file(for a relative path that exists).catalso works.Expected behavior
Access to these files should not be possible.
Actual behavior
Access to files using relative paths is permitted, allowing access to the entire filesystem.
Note: changing directory into those locations does not work, but reading files without changing directory does.
Behavior without a profile
n/a
Additional context
Environment
Checklist
(removed some non-applicable items)
browser-allow-drm yes/browser-disable-u2f noinfirejail.configto allow DRM/U2F in browsers.@ghost commented on GitHub (Dec 17, 2021):
@WhyNotHugo Nice find! Thanks for reporting.
@rusty-snake I'm new to marking issues to a
milestone. Any thoughts on adding this to 0.9.68? Even when this isn't fixed by then (whenever it comes), it's a nice way to keep track of things.@netblue30 commented on GitHub (Dec 19, 2021):
Fixed:
d2e10f8b72Very cool bug, thanks!
@WhyNotHugo commented on GitHub (Dec 20, 2021):
The command in the example above no longer works:
@kmk3 commented on GitHub (Dec 23, 2021):
@WhyNotHugo commented on Dec 20:
Hello, could you open a new issue for this?
@Ding-yixia commented on GitHub (Dec 25, 2023):
这个问题还没有修复