Skip to content

🛡️ Sentinel: [CRITICAL] Fix insecure session file persistence#752

Open
kevinaboos wants to merge 1 commit intomainfrom
sentinel-secure-persistence-17187642287887974361
Open

🛡️ Sentinel: [CRITICAL] Fix insecure session file persistence#752
kevinaboos wants to merge 1 commit intomainfrom
sentinel-secure-persistence-17187642287887974361

Conversation

@kevinaboos
Copy link
Member

🚨 Severity: HIGH
💡 Vulnerability: The save_session and save_latest_user_id functions in src/persistence/matrix_state.rs were using tokio::fs::write, which writes files with default permissions (potentially world-readable depending on umask) and is not atomic. The session file contains sensitive information, including the database passphrase.
🎯 Impact: Local attackers with access to the filesystem could read the session file and extract the database passphrase or hijack the user session.
🔧 Fix: Implemented write_file_securely in src/persistence/utils.rs which:
1. Writes to a temporary file with 0o600 permissions (Unix).
2. Atomically renames the temporary file to the target path.
Updated matrix_state.rs to use this secure writing method.
✅ Verification: Added a unit test in src/persistence/utils.rs verifying that files are created with correct permissions (0o600 on Unix) and content is written correctly. Verified with cargo test persistence::utils.


PR created automatically by Jules for task 17187642287887974361 started by @kevinaboos

…tricted permissions

Co-authored-by: kevinaboos <1139460+kevinaboos@users.noreply.github.com>
@google-labs-jules
Copy link
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

Comments