Skip to content

🔒 Security: Use secure user lookup instead of USER env var#67

Closed
google-labs-jules[bot] wants to merge 1 commit intomainfrom
security-fix-user-retrieval-11088404572518204373
Closed

🔒 Security: Use secure user lookup instead of USER env var#67
google-labs-jules[bot] wants to merge 1 commit intomainfrom
security-fix-user-retrieval-11088404572518204373

Conversation

@google-labs-jules
Copy link
Contributor

Fixed security vulnerability by replacing std::env::var("USER") with secure user lookup using nix crate. Added nix dependency.


PR created automatically by Jules for task 11088404572518204373 started by @jotuel

This change addresses a security vulnerability where the `USER` environment variable was used to determine the current user identity. This variable can be spoofed by an attacker, potentially leading to privilege escalation or unauthorized actions.

We now use `nix::unistd::User::from_uid(Uid::current())` to securely determine the current user based on the effective user ID. This ensures that the application operates on the correct user account.

The `nix` dependency was added to `Cargo.toml` to support this functionality.

The logic in `src/app/mod.rs` was updated in two places:
1. Initializing `selected_user`.
2. Fallback logic when `AccountsService` returns no users.

Verification:
- `cargo check` passes.
- `cargo test` passes.
- Dependencies installed: `libxkbcommon-dev`, `libdbus-1-dev`, `libglib2.0-dev`, `libwayland-dev`.
@google-labs-jules
Copy link
Contributor Author

👋 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.

@jotuel jotuel closed this Feb 18, 2026
@jotuel jotuel deleted the security-fix-user-retrieval-11088404572518204373 branch February 19, 2026 17:08
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