Description
is_path_trusted in scripts/iib/api.py compares the requested path against each allowed parent directory with path.startswith(parent_path), without appending a path separator. A directory whose name merely begins with an allowed path therefore satisfies the comparison, so where /data/images is allowed a request for /data/images_private/secret.txt is treated as trusted and served by FileResponse, disclosing files the confinement was meant to exclude. Whether the check applies depends on get_enable_access_control in scripts/iib/tool.py: it returns true when IIB_ACCESS_CONTROL is set to enable, false when set to disable, and otherwise true when the host Stable Diffusion WebUI was started with share, ngrok, listen or server_name, falling back to false. Confinement is therefore active in the network-exposed WebUI deployments that rely on it, while a standalone run with no such option serves every readable file regardless of this flaw. The fix compares against parent_path joined with os.sep.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| zanllp | infinite-image-browsing | ≤ 1.8.0 | — |
References
- GitHub Issue #968 issue-tracking
- GitHub Pull Request #969 issue-tracking patch
- Fix path traversal in is_path_trusted (CWE-22/CWE-59) patch
- is_path_trusted prefix comparison without a trailing separator at v1.8.0 technical-description
- https://github.com/zanllp/infinite-image-browsing product
- VulnCheck Advisory: Infinite Image Browsing is_path_trusted Prefix Comparison Omits the Trailing Path Separator third-party-advisory