نسخههای متأثر
- نسخههای متأثر
- <= 0.7.5
- نسخهٔ اصلاحشده
- 0.7.6
بهرهبرداری
شرح آسیبپذیری
Summary
Workspace boundary enforcement currently has three related bypass risks. This issue tracks fixing all three in one pull request.
Details
R1 - Dangling Symlink Component Bypass
What happens: Path validation can miss dangling symlink components during traversal checks.
Why it matters: A symlink that is unresolved at validation time can later resolve to an external location.
Impact: Read and write operations may escape workspace boundaries.
Affected area: src/security/path.rs (check_symlink_escape).
R2 - TOCTOU Between Validation and Use
What happens: The path is validated first, then used later for filesystem operations.
Why it matters: A concurrent filesystem change can swap path components after validation but before open/write.
Impact: Race-based workspace escape is possible.
Affected area: Filesystem and file-consuming tools that call validate_path_in_workspace before I/O.
R3 - Hardlink Alias Bypass
What happens: A file inside workspace can be a hardlink to an inode outside the intended workspace trust boundary.
Why it matters: Prefix and symlink checks can pass while data access still mutates or reads external content.
Impact: Policy bypass for read/write operations.
Affected area: Any tool that reads or writes via validated paths.
Risk Matrix
| ID | Risk | Severity | Likelihood | Impact |
|---|---|---|---|---|
| R1 | Dangling symlink component bypass | High | Medium | Workspace boundary escape for read/write |
| R2 | Validate/use TOCTOU race | High | Medium | Race-based boundary escape during file I/O |
| R3 | Hardlink alias bypass | Medium | Low-Medium | External inode read/write through in-workspace path |
PoC
R1 - Dangling symlink component bypass
Create a symlink inside workspace pointing to a missing target.
Validate a path traversing that symlink.
Create the target directory outside workspace after validation.
Perform file operation and observe potential boundary escape if not fail-closed.
R2 - TOCTOU between validation and use
Validate a candidate in-workspace path.
Before open/write, replace an intermediate component with a link to external location.
Continue with the file operation.
Observe boundary escape if operation trusts only stale validation result.
R3 - Hardlink alias bypass
Place a hardlink inside workspace that points to an external inode.
Validate the in-workspace hardlink path.
Read or write through this path.
Observe external inode access through a path that appears in-scope.
Impacts
Unauthorized cross path boundary
Credit
Patch
پیوندها
- https://github.com/advisories/GHSA-2m67-cxxq-c3h8
- https://github.com/qhkm/zeptoclaw
- https://github.com/qhkm/zeptoclaw/commit/bf004a20d3687a0c1a9e052ec79536e30d6de134
- https://github.com/qhkm/zeptoclaw/commit/f50c17e11ae3e2d40c96730abac41974ef2ee2a8
- https://github.com/qhkm/zeptoclaw/pull/324
- https://github.com/qhkm/zeptoclaw/releases/tag/v0.7.6
- https://github.com/qhkm/zeptoclaw/security/advisories/GHSA-2m67-cxxq-c3h8
- https://nvd.nist.gov/vuln/detail/CVE-2026-32232
گزارشدهندگان
- zpbrent

