boto3 1.43.116

Source: https://github.com/boto/boto3
Tag scanned: 1.43.116
Compared with: 1.43.115 (0 signals introduced since)
Files: 202 scanned, 37 skipped (binary, oversized, or unrecognised)
Signals: 0 critical · 0 warn · 1 info
Scan time: 3.5 s
LLM review: Reviewed by claude-haiku-5-5 (Anthropic): 1 of 1 warn and critical signal; 1 demoted to info.
Disclude version: 4.0.0
Scanned (UTC): 2026-10-21 00:56

Signals

Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.

info ~~warn~~ → info by review dynamic-execution scripts/new-change:123:13

`subprocess.Popen` called with `shell=True` and a literal command (ast pass, confidence 0.70)
```
        editor = env.get('VISUAL', env.get('EDITOR', 'vim'))
        p = subprocess.Popen(f'{editor} {f.name}', shell=True)
        p.communicate()
        with open(f.name) as f:
```
likely benign LLM, confidence 0.90 A changelog helper script launches the user's editor via subprocess.Popen with shell=True, using the EDITOR/VISUAL environment variable and a temp file name.
Reasoning
The shell=True call builds its command from the user's VISUAL/EDITOR environment variable and a temp file name, which is the conventional way to launch an editor. The command is not fetched from the network, decoded, or otherwise attacker-controlled. The finding's message says 'literal command' but the string is an f-string built from env values; the risk is a shell-injection footgun at most, not malicious intent. This is a typical developer script pattern.

Reproduce This Scan

Run disclude locally to verify. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.

cargo install disclude --version 4.0.0
git clone https://github.com/boto/boto3 boto3 && cd boto3
git checkout 1.43.116
disclude scan --severity info --diff 1.43.115 .