botocore 1.43.114
- Source
- https://github.com/boto/botocore
- Tag scanned
1.43.114- Compared with
1.43.113(0 signals introduced since)- Files
- 331 scanned, 3148 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 30 info
- Scan time
- 22.5 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-15 16:11
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.py helper that imports a module by name via __import__.Reasoning
This is the standard six.py import_module helper, which calls __import__ on a caller-supplied name. Dynamic import is expected in a vendored compatibility library and the function has no encoded payload or hidden trigger.
-
= =likely benign Vendored six.py exec_ helper reading the caller's frame globals.Reasoning
This is six's exec_ helper fallback that uses sys._getframe to read caller globals when none are passed. It is a known legitimate pattern in six; the anti-analysis label is a heuristic false positive from the file containing exec.
-
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 Launches the user's editor on a temp file via shell=True.Reasoning
The shell=True command interpolates the user's EDITOR/VISUAL environment variable to open a changelog file. This is a common editor-launch idiom with no attacker-controlled remote input, though shell=True with an interpolated filename is a minor injection risk.
-
= f = assert ==likely benign Test decompresses a recorded request body to verify its contents.Reasoning
This is a test asserting that a gzip-compressed request body decodes to the expected serialized params. Decompressing a stubbed HTTP body in a test is ordinary and contains no hidden payload.
-
: , : , }, ),likely benign Expected base64 SHA256 checksum header value in a test.Reasoning
This is a documented AWS SHA256 checksum value (base64 of a digest) used as an expected header in a test fixture. Base64 checksums are normal here.
-
: , : , }, ),likely benign Expected base64 SHA512 checksum header value in a test.Reasoning
This is a standard base64-encoded SHA512 checksum value used as an expected header in a test fixture.
-
, ),likely benign Expected base64 SHA256 checksum header value in a test.Reasoning
Repeat of the same legitimate SHA256 checksum fixture value in a test.
-
, ),likely benign Expected base64 SHA512 checksum header value in a test.Reasoning
Repeat of the same legitimate SHA512 checksum fixture value in a test.
-
, ),likely benign Expected base64 SHA256 checksum header value in a test.Reasoning
Repeat of the same legitimate SHA256 checksum fixture value in a test.
-
, ),likely benign Expected base64 SHA512 checksum header value in a test.Reasoning
Repeat of the same legitimate SHA512 checksum fixture value in a test.
-
, , ),likely benign Expected base64 SHA256 checksum in a parametrized test.Reasoning
Legitimate SHA256 checksum test fixture value, paired with a deliberately wrong checksum for a negative case.
-
, , ), ]likely benign Expected base64 SHA512 checksum in a parametrized test.Reasoning
Legitimate SHA512 checksum test fixture value in a parametrized test.
-
info
warn→ info by reviewencoding-base64tests/unit/auth/aws4_testsuite/post-sts-token/readme.txt:15:1AQoDYXdzEPT//////////wEXAMPLEtc764bNrC9SAPBSM22wDOk4x4HIZ8j4FZTwdQWLWsKWHGBuFqwAeMicRXmxfpSPfIeoIYRqTflfKD8YUuwthAx7mSEI/qkPpKPi/kMcGdQrmGdeehM4IC1NtBmUpp2wUE8phUZampKsburEDy0KPkyQDYwT7WZ0wq5VSXDvp75YU9HFvlRd8Tx6q6fE8YQcHNVXAkiY9q6d+xo0rKwT38xVqr7ZD0u0iPPkUL64lIZbqBAz+scqKmlzm8FDrypNC9Yjc8fPOLn9FX9KSYvKTr4rvx3iSIlTJabIlikely benign Sample AWS STS session token in SigV4 test suite readme.Reasoning
This is an AWS documentation example security token from the official SigV4 test suite, a sample credential with EXAMPLE markers. It is test data, not a payload.
-
, , )likely benign Expected base64 digest value in a signer unit test.Reasoning
This is a base64 SHA256 digest of a test string used as an expected signing/checksum value in a unit test. Expected test data.
-
, , )likely benign Expected HMAC signature test vector in a signer unit test.Reasoning
The blob is an expected HMAC-SHA256 signature value in a unit test asserting the signer's output. Test vectors like this are normal in an SDK test suite and carry no obfuscation.
-
: , : , } =likely benign Expected signature constant in a signer test.Reasoning
The base64 value is the expected signature in a test that checks calc_signature output. This is a legitimate fixture from a botocore-style test suite.
-
, , )likely benign Expected signature value in a tuple assertion.Reasoning
The value is the expected signature paired with a canonical query string in an assertion. It is a test vector and not a payload.
-
, , )likely benign Expected signature in a params-based signer test.Reasoning
This is an expected HmacSHA256 signature compared against request parameters in a unit test. It is ordinary test data.
-
), )likely benign Expected signature inside an authorization header assertion.Reasoning
The value is an expected Signature field embedded in an AWS3-HTTPS authorization header string inside an assertion. This is a test fixture.
-
: , : , :likely benign Placeholder bearer token with a joking base64 value.Reasoning
The token decodes to the plain text 'you're not supposed to decode this!', a deliberately joking placeholder used as a bearer token in test data. It is not a hidden payload.
-
: , },likely benign Expected Bearer authorization header in a test case.Reasoning
This is the expected Authorization header built from the same placeholder token in a test case. It is benign test data.
-
=likely benign Gzip-compressed request body fixture in a compression test.Reasoning
The bytes literal begins with the gzip magic header and is a recorded compressed request body used for a compression test. Binary fixtures like this are expected in this context.
-
likely benign Binary event-stream header fixture for a parser test.
Reasoning
The escapes encode event-stream binary header bytes (name/type/length fields) for a parser test. Serialized binary fixtures are the normal way to test this format.
-
=likely benign Encoded event-stream headers fixture in a test.Reasoning
This is another encoded event-stream header fixture with the same structure, used to test header parsing. It is benign test data.
-
, ,likely benign Expected checksum digest vectors in a checksum test table.Reasoning
These are expected base64 digests of known test input for SHA-1 and SHA-256 checksum tests. They are standard test vectors.
-
, , ), ]likely benign Expected SHA-512 digest vector in a checksum test table.Reasoning
This is the expected SHA-512 base64 digest in the same checksum test table. It is a standard test vector.
-
= =likely benign Base64 pagination token fixture in a paginator test.Reasoning
The base64 decodes to a JSON pagination token with boto-encoded keys, used as input to a paginator test. It is a documented token format, not hidden code.
-
=likely benign Multi-part base64 pagination token fixture in a test.Reasoning
This is a multi-part base64 pagination token that decodes to JSON state for a paginator test. It is ordinary test input.
-
=likely benign Base64-encoded JSON pagination token used as test fixture data in a paginator unit test.Reasoning
The raw pass flagged a base64 string split across lines in a unit test. The blob decodes to a JSON pagination token (boto_encoded_keys plus nested base64 values 'YmFt'/'YmF6' for b'bam'/b'baz'), which matches the test's expected dict. This is test fixture data for a paginator, not obfuscation. Raw-pass findings have a high false-positive rate, and the context makes the benign reading clear.
-
) =likely benign Second segment of the same base64 pagination token fixture in a paginator unit test.Reasoning
This is the second half of the same base64 pagination token flagged at line 63. It decodes to the same boto-style JSON continuation token and is asserted against the expected dict on the following line. It is a legitimate test fixture, not a payload.
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.
&&