botocore 1.43.115
- Source
- https://github.com/boto/botocore
- Tag scanned
1.43.115- Compared with
1.43.114(0 signals introduced since)- Files
- 331 scanned, 3148 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 30 info
- Scan time
- 25.4 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 30 of 30 warn and critical signals; 30 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-20 00:41
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
"""Import module, returning the module after the last dot.""" returnlikely benign Vendored six compatibility helper that imports a module by dynamic name.Reasoning
This is the standard six.py `_import_module` helper, which imports a module by name. The non-literal __import__ is expected for a compatibility library that loads modules dynamically. The name is internal, not attacker-controlled input.
-
= =likely benign Vendored six exec_ shim reading caller frame globals for exec in the calling namespace.Reasoning
This is the well-known six.py exec_ helper that reads caller globals/locals via sys._getframe(1) to execute code in the caller's namespace. It is a standard, documented compatibility shim, and the anti-analysis heuristic is a false match on the file-level exec usage.
-
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 Dev script launching the user's editor through a shell command.Reasoning
This is a developer script that opens the user's configured $VISUAL or $EDITOR in a shell command. The command comes from the local environment and the temp file name, so shell=True is a convenience, not a remote attack vector.
-
= f = assert ==likely benign Test decompressing a gzip request body to verify its contents.Reasoning
This is a test asserting that a request body compressed with gzip decompresses to the expected serialized params. Decompressing a response in a test is ordinary and not a hidden payload.
-
: , : , }, ),likely benign Base64-encoded SHA256 checksum literal in an HTTP checksum test.Reasoning
This is an AWS SHA256 checksum value (base64 of 32 bytes) used as an expected header in a test vector. Checksums in test fixtures are normal.
-
: , : , }, ),likely benign Base64-encoded SHA512 checksum literal in an HTTP checksum test.Reasoning
This is a SHA512 checksum base64 literal used as an expected header value in a test fixture, which is normal for checksum testing.
-
, ),likely benign Repeated base64 SHA256 checksum literal in a test fixture.Reasoning
Same SHA256 checksum literal reused as an expected header value in a test case. Benign test data.
-
, ),likely benign Repeated base64 SHA512 checksum literal in a test fixture.Reasoning
Same SHA512 checksum literal reused in a test case. Benign test data.
-
, ),likely benign Repeated base64 SHA256 checksum literal in a test fixture.Reasoning
Repeated SHA256 checksum literal in a test fixture. Benign.
-
, ),likely benign Repeated base64 SHA512 checksum literal in a test fixture.Reasoning
Repeated SHA512 checksum literal in a test fixture. Benign.
-
, , ),likely benign Base64 SHA256 checksum literal in parametrized checksum tests.Reasoning
SHA256 checksum literal used as parametrized test input alongside a 'not-a-checksum' value. Clearly test data.
-
, , ), ]likely benign Base64 SHA512 checksum literal in parametrized checksum tests.Reasoning
SHA512 checksum literal in parametrized checksum test data. Benign.
-
info
warn→ info by reviewencoding-base64tests/unit/auth/aws4_testsuite/post-sts-token/readme.txt:15:1AQoDYXdzEPT//////////wEXAMPLEtc764bNrC9SAPBSM22wDOk4x4HIZ8j4FZTwdQWLWsKWHGBuFqwAeMicRXmxfpSPfIeoIYRqTflfKD8YUuwthAx7mSEI/qkPpKPi/kMcGdQrmGdeehM4IC1NtBmUpp2wUE8phUZampKsburEDy0KPkyQDYwT7WZ0wq5VSXDvp75YU9HFvlRd8Tx6q6fE8YQcHNVXAkiY9q6d+xo0rKwT38xVqr7ZD0u0iPPkUL64lIZbqBAz+scqKmlzm8FDrypNC9Yjc8fPOLn9FX9KSYvKTr4rvx3iSIlTJabIlikely benign Example AWS STS session token in an SigV4 test suite readme.Reasoning
This is an AWS Signature V4 example security token from the official test suite, with EXAMPLE markers in it. It is documentation/test data, not an embedded payload.
-
, , )likely benign Base64 expected signature value in a signer unit test.Reasoning
This is a base64 expected output for a URL-encoded HMAC/signature test vector. Test expectation data, benign.
-
, , )dismissed Expected HMAC signature constant in a signer unit test.Reasoning
Raw-pass base64 match on a 44-byte HMAC-SHA256 signature literal compared against computed output in a unit test. Signature fixtures are expected test data, and the raw pass has a high false-positive rate.
-
: , : , } =dismissed Signature test vector in a signer test's params dict.Reasoning
A base64 signature value placed in a request params dict inside a test case that calls calc_signature. This is a fixed test vector, not a payload or dropper.
-
, , )dismissed Expected signature in an assertEqual in a signer test.Reasoning
The base64 value is the expected signature in an assertEqual tuple after a signing call. This is a standard test assertion.
-
, , )dismissed Expected signature constant asserted in a signer test.Reasoning
Same pattern as the other signer tests: a fixed expected signature compared against the output of the signing code under test.
-
), )dismissed Expected AWS3 signature header value in a test string.Reasoning
Inside a test string literal, a base64-like signature component of an AWS3-HTTPS authorization header. It is an expected header value in a test.
-
: , : , :likely benign Placeholder bearer token fixture in an auth test.Reasoning
The value decodes to a joke string ('you're not supposed to decode this!') and is used as a bearer token fixture in a parameterized auth test. It is a placeholder with no malicious function.
-
: , },likely benign Expected Bearer header containing the placeholder token.Reasoning
The same placeholder token appears in the expected Authorization header of the test case. It is a consistent test fixture.
-
=likely benign Gzip-compressed request body fixture for a compression test.Reasoning
A bytes literal of a gzip stream used as a request body fixture for compression tests. Binary payload shape is expected because the test verifies compressed output.
-
likely benign Binary eventstream header fixture for parser tests.
Reasoning
Hand-built binary eventstream header bytes used to exercise a protocol parser. This is required test data for binary wire-format decoding.
-
=likely benign Binary eventstream headers fixture in a test.Reasoning
Binary header-encoding bytes in a test fixture for the eventstream parser. Escaped bytes are the natural way to express a binary wire format.
-
, ,dismissed Expected checksum digest values in a parameterized test table.Reasoning
Base64 digests of known inputs, listed as a table of (checksum class, expected value) pairs for a checksum test. These are expected test vectors.
-
, , ), ]dismissed Expected SHA-512 digest value in a checksum test table.Reasoning
The final entry of the same expected-digest table, a base64 SHA-512 value. It is a test vector with no execution or exfiltration role.
-
= =dismissed Encoded pagination token fixture in a paginator test.Reasoning
A base64 pagination token that decodes to JSON with encoded keys, used as input to the paginator's token decoding. It is a test fixture for a legitimate feature.
-
=dismissed Multi-line encoded pagination token in a paginator test.Reasoning
A multi-part base64 pagination token passed to paginator decoding. It is test data for a documented pagination mechanism.
-
=dismissed Base64-encoded JSON pagination token used as test fixture data in test_paginate.py.Reasoning
Raw-pass base64 hit in a unit test. The blob decodes to a JSON pagination token containing a 'boto_encoded_keys' field and nested 'foo'/'bin'/'bar' keys, with values that are themselves base64. This is a deliberately constructed test fixture for pagination-token round-tripping, not a payload. The file is a test, the content is readable structured data, and the raw pass has a high false-positive rate for base64-looking strings.
-
) =dismissed Second half of the same base64 pagination-token fixture, followed by an expected-value assertion in a unit test.Reasoning
This is the continuation of the same split base64 string literal, which concatenates into the same pagination-token fixture. The following line asserts the expected decoded dict {'foo': {'bar': b'baz', 'bin': b'bam'}}, confirming the blob is round-trip test data for a paginator's encoded-keys feature. No execution or decoding of untrusted input is present.
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.
&&