`~/Library` carve-outs are read-write
Nobody has claimed this yet.
- Dominant language
- Nix
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
~/Library/Application Support and ~/Library/Caches are file*, not read-only
(allow file* (subpath (string-append user_home "/Library/Application Support")))
(allow file* (subpath (string-append user_home "/Library/Caches")))
These grant read and write to paths holding browser cookie databases, Slack and Discord tokens, and editor state. Combined with (allow network*), a compromised dev tool inside the sandbox can read browser cookies and send them out. The write half also allows planting files in e.g. Application Support/Code/User/ that later execute unsandboxed.
Read-only would close the write vector. Narrowing to the specific subpaths shells actually need would be better still.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the sandbox policy containing the two (allow file* ...) rules for ~/Library/Application Support and ~/Library/Caches, then inspect how shell access to those paths is used. Done means those paths no longer permit writes while the specific access shells require remains available.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100