Skip to content

πŸ›‘οΈ Sentinel: [CRITICAL] Fix path traversal in snapshot management#22

Open
bitcoiner-dev wants to merge 1 commit intomasterfrom
sentinel-fix-snapshot-path-traversal-1676231061828451625
Open

πŸ›‘οΈ Sentinel: [CRITICAL] Fix path traversal in snapshot management#22
bitcoiner-dev wants to merge 1 commit intomasterfrom
sentinel-fix-snapshot-path-traversal-1676231061828451625

Conversation

@bitcoiner-dev
Copy link
Copy Markdown
Owner

🚨 Severity: CRITICAL

πŸ’‘ Vulnerability: The snapshot management command blindly joined user-provided snapshot names directly to the snapshot directory (snap_dir.join(format!("{name}.json"))). This allowed a path traversal vulnerability where inputs like ../ could be used to manipulate files outside of the intended directory.

🎯 Impact: If exploited, this could lead to arbitrary file reads (via Restore) or arbitrary file overwriting (via Save), potentially exposing sensitive user data or corrupting the configuration.

πŸ”§ Fix: Implemented an explicit allowlist validation function (crate::utils::validate_file_name) that strictly restricts filenames to alphanumeric characters, dashes, and underscores. Applied this validation proactively in the snapshot Save and Restore operations.

βœ… Verification: Unit tests have been added to ensure the validation rejects malicious inputs (like ../ and /etc). The full zinc-wallet-cli test suite was run and passed successfully.


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

- Added `validate_file_name` in `src/utils.rs` with strict alphanumeric/dash/underscore allowlist.
- Validated user input for both snapshot Save and Restore actions to prevent path traversal vectors.

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