Skip to content

πŸ›‘οΈ Sentinel: [MEDIUM] Fix insecure snapshot directory permissions#15

Open
bitcoiner-dev wants to merge 1 commit intomasterfrom
sentinel-fix-snapshot-dir-permissions-13216546673017836747
Open

πŸ›‘οΈ Sentinel: [MEDIUM] Fix insecure snapshot directory permissions#15
bitcoiner-dev wants to merge 1 commit intomasterfrom
sentinel-fix-snapshot-dir-permissions-13216546673017836747

Conversation

@bitcoiner-dev
Copy link
Copy Markdown
Owner

🚨 Severity: MEDIUM
πŸ’‘ Vulnerability: The snapshot directory containing sensitive wallet state and backups was created using the standard std::fs::create_dir_all function without explicitly setting file permissions. This relies on the default process umask.
🎯 Impact: Depending on the host machine's configuration, the snapshot directory might be readable or writable by other non-privileged users on the system, potentially exposing wallet keys and metadata.
πŸ”§ Fix: Used the existing utility crate::paths::create_secure_dir_all instead. This utility wraps DirBuilderExt to explicitly set mode(0o700) on Unix systems, locking down directory access to only the owning user.
βœ… Verification: Ran cargo test and cargo check to ensure correctness. Verified that create_secure_dir_all is properly mapped and invoked.


PR created automatically by Jules for task 13216546673017836747 started by @bitcoiner-dev

Replaced standard `fs::create_dir_all` with the existing `create_secure_dir_all` wrapper in `src/commands/snapshot.rs`.
This ensures that the sensitive wallet snapshots directories are created with strict (0o700) file permissions, instead of relying on the default umask.

Co-authored-by: bitcoiner-dev <75873427+bitcoiner-dev@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

πŸ‘‹ Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a πŸ‘€ emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

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 this pull request may close these issues.

1 participant