Skip to content

🛡️ Sentinel: [HIGH] Fix null byte path truncation vulnerability#3582

Closed
EffortlessSteven wants to merge 1 commit into
mainfrom
jules-5554472715702630567-033e80c7
Closed

🛡️ Sentinel: [HIGH] Fix null byte path truncation vulnerability#3582
EffortlessSteven wants to merge 1 commit into
mainfrom
jules-5554472715702630567-033e80c7

Conversation

@EffortlessSteven
Copy link
Copy Markdown
Member

🚨 Severity: HIGH
💡 Vulnerability: The validate_model_request function validated file extensions (e.g., .gguf) using Rust's .ends_with(), but failed to reject null bytes (\0). This allowed path truncation attacks where a path like secret.txt\0.gguf passes the extension check but is truncated to secret.txt when passed to underlying C/OS APIs.
🎯 Impact: Attackers could bypass path validation to load arbitrary files or probe for file existence on the filesystem.
🔧 Fix: Explicitly check for and reject null bytes in the model path before performing extension or directory validation.
✅ Verification: Run cargo test -p bitnet-server --lib security::tests::test_model_path_null_byte_rejection.


PR created automatically by Jules for task 5554472715702630567 started by @EffortlessSteven

Added check to explicitly reject null bytes (`\0`) in `validate_model_request`
to prevent attackers from bypassing `.ends_with(".gguf")` extension checks
via path truncation when the path is passed to underlying C/OS APIs.
@google-labs-jules
Copy link
Copy Markdown

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

@gemini-code-assist
Copy link
Copy Markdown

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 25, 2026

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9e67c3db-23ca-4b49-884f-a4b50d7490e0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jules-5554472715702630567-033e80c7

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@EffortlessSteven
Copy link
Copy Markdown
Member Author

Closing as superseded by #3626.

Reason: duplicate null-byte model path validation fix. The canonical PR is ledger-aligned under TRUTH-003, includes regression coverage, and is recorded in the alignment tracker.

@google-labs-jules
Copy link
Copy Markdown

Closing as superseded by #3626.

Reason: duplicate null-byte model path validation fix. The canonical PR is ledger-aligned under TRUTH-003, includes regression coverage, and is recorded in the alignment tracker.

Understood. Acknowledging that this work is now obsolete and stopping work on 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