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
- 209 scanned, 30 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 3 info
- Scan time
- 4.6 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 2 of 2 warn and critical signals; 2 demoted to info.
- Disclude version
- 4.1.0
- Scanned (UTC)
- 2026-10-21 19:58
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
dismissed Inline SVG path data for an icon in a Sphinx documentation template.
Reasoning
A 2058-character line containing SVG path data in an HTML template is a typical inlined icon or graphic. Long lines of path coordinates are common in generated SVG and carry no obfuscation or malicious payload; the raw pass has a high false-positive rate for this pattern.
-
-
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 Helper script launches the user's editor via a shell command built from EDITOR/VISUAL and a temp filename.Reasoning
The shell=True call runs an f-string built from the VISUAL/EDITOR environment variables and a temp file name. This is a developer helper that opens an editor, so the command is user-controlled from the local environment rather than attacker-supplied. The shell=True usage with an interpolated filename is a real quoting/injection hazard, but it is a legitimate pattern for launching an editor and does not show malicious intent.
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.
&&