fix(patch): cherry-pick 9ca7300 to release/v0.27.1-pr-18395 to patch version v0.27.1 and create version 0.27.2

[gemini-cli-robot]

This PR automatically cherry-picks commit 9ca7300 to patch version v0.27.1 in the stable release to create version 0.27.2.

[gemini-code-assist]

Summary of Changes

Hello @gemini-cli-robot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request is an automated patch release that addresses a critical issue where path validation was being prematurely bypassed under specific conditions. By removing an incorrect early exit, the change ensures that all paths are consistently and thoroughly validated, thereby enhancing the overall robustness and security of path handling within the application.

Highlights

• Path Validation Logic Refinement: An early exit condition in the isPathAllowed method within packages/core/src/config/config.ts has been removed. Previously, if the application was in interactive mode and the path was absolute, the method would immediately return true, bypassing the full path resolution and validation process. This change ensures that all paths now consistently undergo the complete validation logic.

Changelog

• packages/core/src/config/config.ts
  • Removed an if condition in the isPathAllowed method that incorrectly allowed absolute paths to bypass full validation when the application was in interactive mode.

Activity

• This pull request was automatically generated by gemini-cli-robot.
• It cherry-picks commit 9ca7300c90e6cf407bde5c8b1c9d7fbf74736968 to the release/v0.27.1-pr-18395 branch.
• The purpose is to create a new patch version 0.27.2 based on v0.27.1.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request cherry-picks a critical security fix. It addresses a critical path traversal vulnerability where the isPathAllowed method in the Config class incorrectly allowed access to any absolute path when running in interactive mode, effectively bypassing workspace constraints. This flaw could have been exploited by a malicious actor to access or modify sensitive system files outside the designated workspace. The change removes this condition, ensuring all file paths are now correctly validated against the workspace, mitigating the vulnerability.

I am having trouble creating individual review comments. Click here to see my feedback.

packages/core/src/config/config.ts (1714-1716)

The code previously allowed any absolute path to be considered 'allowed' if the session was interactive. This created a significant security bypass, as an attacker (e.g., via prompt injection) could force the tool to access or modify sensitive files outside the intended workspace by providing an absolute path. Removing this check ensures that all paths, including absolute ones, are subject to proper workspace boundary validation.

References

1. Sanitize user-provided file paths used in file system operations to prevent path traversal vulnerabilities.
2. Utility functions that perform file system operations should validate their path inputs internally to prevent path traversal vulnerabilities, rather than relying solely on callers to perform validation.

[github-actions]

Size Change: -103 B (0%)

Total Size: 23.5 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	23.5 MB	-103 B (0%)
./bundle/sandbox-macos-permissive-closed.sb	1.03 kB	0 B
./bundle/sandbox-macos-permissive-open.sb	890 B	0 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB	0 B
./bundle/sandbox-macos-restrictive-closed.sb	3.29 kB	0 B
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB	0 B
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB	0 B

_{compressed-size-action}