- Edited
Create a profile named /../../../a
Profile ends up in ~/Applications/a.app
other examples:
Other profile names that include :
, /
and .
may result in the .app
suffix not being created, or otherwise not launching the profile app because the location is incorrect
It can also overwrite existing apps too. Suppose you have an app called ~/Applications/a.app
, and you create the profile with the name /../../../../a.app
then the app gets completely messed up
Proposed solution:
Disallow .
, :
and /
from profile names, and instead show an error to the user.
.
could result in unintended behavior if profile name starts with a .
, making it hidden
:
and /
are both path separators in macos, and would cause confusion bc of the internal vs visualization in Finder would differ.
this way, path traversal is impossible
0.99.128.2-rc (WebKit 619.1.11.111.2)
Sonoma (14)