Evidence · DiggingBeagle record
Chrome DevTools MCP screenshot target-path bypass advisory
Maintainer disclosure of extension handling and symlink path validation performed in the wrong order.
- Source role
- primary disclosure
Evidence record
Maintainer disclosure of extension handling and symlink path validation performed in the wrong order.
Claim-level citations (2)
- supportsChrome DevTools MCP screenshot extension handling could escape a path allowlist: The Chrome DevTools MCP advisory describes validating a screenshot pathname before extension insertion and final symlink resolution, enabling an out-of-root write under an attacker-influenced path.
GHSA-5hw5-4q87-m6x9: ensureExtension, symlink path and fixed release
- supportsChrome DevTools MCP screenshot extension handling could escape a path allowlist: Chrome DevTools MCP checked an output path against an allowed workspace before appending an image extension and following a symlink. The attacker needed control of the relevant screenshot output path and a target outside the intended allowed root. A path accepted before extension handling could resolve to another file location for the final image write.
GHSA-5hw5-4q87-m6x9: ensureExtension, symlink path and fixed release