Skip to content

πŸ›‘οΈ Sentinel: [CRITICAL] Fix path traversal in LocalJsonStore#334

Draft
hackerxj2010 wants to merge 1 commit into
mainfrom
sentinel/fix-path-traversal-local-json-store-3938900156797340834
Draft

πŸ›‘οΈ Sentinel: [CRITICAL] Fix path traversal in LocalJsonStore#334
hackerxj2010 wants to merge 1 commit into
mainfrom
sentinel/fix-path-traversal-local-json-store-3938900156797340834

Conversation

@hackerxj2010

Copy link
Copy Markdown
Owner

I have fixed a critical path traversal vulnerability in the `LocalJsonStore` class within the `@jeanbot/documents` package.

🚨 Severity: CRITICAL

πŸ’‘ Vulnerability: Path Traversal

🎯 Impact:

An attacker could use a malicious key (e.g., `../../../etc/passwd`) to read or write arbitrary JSON-formatted files on the server's filesystem, escaping the intended storage directory.

πŸ”§ Fix:

  • Modified the `toPath` method in `packages/documents/src/index.ts` to use `path.resolve` for absolute path resolution.
  • Added validation using `path.relative` to confirm the resolved path is contained within the `baseDirectory`.
  • Improved key splitting to handle both `/` and `\` as separators.
  • Added a new unit test `tests/unit/local-json-store.test.ts` covering path traversal and prefix bypass scenarios.

βœ… Verification:

  • Ran the new unit tests: `pnpm test tests/unit/local-json-store.test.ts` (passed).
  • Ran all workspace tests: `pnpm test` (passed).
  • Verified manually that files can no longer be written outside the base directory using traversal keys.

PR created automatically by Jules for task 3938900156797340834 started by @hackerxj2010

- Implemented robust path validation in \`LocalJsonStore\` to prevent escaping the base directory.
- Used \`path.resolve\` and \`path.relative\` to ensure the resolved path is a child of the intended storage root.
- Added a comprehensive unit test suite in \`tests/unit/local-json-store.test.ts\` to verify the fix and prevent regressions.
- Added security journal entry for the path validation pattern.

Co-authored-by: hackerxj2010 <198651211+hackerxj2010@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