botocore 1.43.113
- Source
- https://github.com/boto/botocore
- Tag scanned
1.43.113- Compared with
1.43.112(0 signals introduced since)- Files
- 331 scanned, 3148 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 30 info
- Scan time
- 28.0 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-14 18: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 library helper that dynamically imports a module by name.Reasoning
This is the standard import helper in the vendored six compatibility library. It calls __import__ on a caller-supplied module name and returns sys.modules, which is the expected pattern for a dynamic-import utility. No payload or obfuscation is visible.
-
= =likely benign Vendored six code reads the caller's frame globals to set up module state.Reasoning
This is six's lazy-module code, which reads the caller's globals via sys._getframe(1) to populate the module namespace. The anti-analysis label comes from generic co-occurrence in a large vendored file, not from anything in this snippet.
-
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 Developer script launches the user's editor via a shell command to edit a temp file.Reasoning
The shell=True call runs an editor taken from the VISUAL/EDITOR environment variables, followed by a temp file name. This is a common and somewhat unsafe editor-launch idiom, but the command comes from the user's own environment and there is no remote input or encoded payload.
-
= f = assert ==likely benign Test decompresses a gzip request body to assert on its contents.Reasoning
This is a functional test that gunzips a recorded HTTP request body in order to compare it against the expected serialized body. Decompression here only checks test output and is not an embedded or hidden payload.
-
: , : , }, ),dismissed Base64 SHA256 checksum string used as expected header value in an HTTP checksum test.Reasoning
The value is a base64-encoded SHA256 checksum that appears as an expected x-amz-checksum header in a test fixture. This is ordinary test data, and the raw base64 heuristic has a high false-positive rate here.
-
: , : , }, ),dismissed Base64 SHA512 checksum string used as expected header value in a test fixture.Reasoning
The value is a base64-encoded SHA512 checksum used as an expected header in a test fixture. It is legitimate test data.
-
, ),dismissed Repeated base64 SHA256 checksum literal in a parametrized checksum test.Reasoning
This is the same SHA256 checksum literal as elsewhere in the test file, used as a parametrized expected header value. It is benign test data.
-
, ),dismissed Repeated base64 SHA512 checksum literal in a parametrized checksum test.Reasoning
This is the same SHA512 checksum literal in a parametrized test expectation. It is benign test data.
-
, ),dismissed Repeated base64 SHA256 checksum literal in a test fixture.Reasoning
This is a repeated SHA256 checksum literal in a test fixture, matching the known expected checksum for the test body. It is benign.
-
, ),dismissed Repeated base64 SHA512 checksum literal in a test fixture.Reasoning
This is a repeated SHA512 checksum literal in a test fixture. It is benign.
-
, , ),dismissed Expected SHA256 checksum literal in a parametrized checksum-mismatch test case.Reasoning
The snippet contains an expected SHA256 checksum literal in a parametrized test case, next to a plain-text 'not-a-checksum' value. This is test data, not a hidden payload.
-
, , ), ]dismissed Expected SHA512 checksum literal in a parametrized checksum-mismatch test case.Reasoning
The snippet contains an expected SHA512 checksum literal in a parametrized test case, next to a base64 'not-a-checksum' value. It is benign test data.
-
info
warn→ info by reviewencoding-base64tests/unit/auth/aws4_testsuite/post-sts-token/readme.txt:15:1AQoDYXdzEPT//////////wEXAMPLEtc764bNrC9SAPBSM22wDOk4x4HIZ8j4FZTwdQWLWsKWHGBuFqwAeMicRXmxfpSPfIeoIYRqTflfKD8YUuwthAx7mSEI/qkPpKPi/kMcGdQrmGdeehM4IC1NtBmUpp2wUE8phUZampKsburEDy0KPkyQDYwT7WZ0wq5VSXDvp75YU9HFvlRd8Tx6q6fE8YQcHNVXAkiY9q6d+xo0rKwT38xVqr7ZD0u0iPPkUL64lIZbqBAz+scqKmlzm8FDrypNC9Yjc8fPOLn9FX9KSYvKTr4rvx3iSIlTJabIdismissed A base64-looking example session token in a botocore aws4 test-suite readme.Reasoning
The blob is the AWS documentation example STS session token from the aws4 test suite, a public sample value rather than a real credential or encoded payload. The readme is a test fixture description, so the base64 match is a false positive from a raw byte-pattern pass.
-
, , )dismissed An expected base64 HMAC signature constant in a SigV2 signer test.Reasoning
The value is an expected HMAC-SHA256 signature string in a signer unit test, compared against computed output. Base64 is the normal output format for signatures, so this is a legitimate test vector.
-
, , )dismissed An expected base64 signature asserted in a signer test.Reasoning
This is an expected Signature value asserted against request data in a signer unit test. It is a legitimate test vector with no obfuscation or malicious behaviour.
-
: , : , } =dismissed A fixed expected signature literal in a signer unit test.Reasoning
The base64 value is an expected signature fixture in a signer test that compares calc_signature output. Signature strings like this are normal in test suites.
-
, , )dismissed An expected base64 signature tuple in a signer test.Reasoning
The same expected signature constant appears in a signer test assertion. It is a fixed test vector for HMAC output.
-
, , )dismissed A base64 expected signature in a signer test assertion.Reasoning
This is an expected signature value compared against request parameters in a test. No execution or hiding of code is involved.
-
), )dismissed An expected base64 signature inside an Authorization header string in a test.Reasoning
The literal is an expected Authorization header signature in a signer test. It is a deterministic test vector, not an encoded payload.
-
: , : , :likely benign A placeholder bearer token in an auth unit test fixture.Reasoning
The token decodes to the plain text "you're not supposed to decode this!", a joke placeholder used as a bearer token fixture. It is a test value with no hidden behaviour.
-
: , },likely benign The expected Bearer header value matching the placeholder test token.Reasoning
This is the expected Authorization header matching the same placeholder token in the bearer auth test. It is a fixture, not a dropper or obfuscated payload.
-
=likely benign A gzip-compressed request body stored as a bytes literal in a compression test.Reasoning
The bytes literal begins with the gzip magic header 1f 8b and holds a pre-compressed request body. It is a fixture for testing compression in a test file, not a concealed payload executed at runtime.
-
likely benign A binary event-stream frame literal used as a parsing test fixture.
Reasoning
The bytes are a binary event-stream frame with length and header fields, used as an expected wire-format fixture in a parser test. The hex escapes reflect binary protocol data, not obfuscation of malicious logic.
-
=likely benign Binary event-stream header fixture bytes in a botocore-style unit test.Reasoning
The snippet is a concatenated bytes literal of binary header records (type/length-prefixed values such as 'bytes' and 'utf8'), which matches a fixture for testing AWS event-stream header parsing in a unit test file. The escapes are expected for binary test data and there is no execution or decoding of a payload.
-
, ,likely benign Base64-encoded SHA-1 and SHA-256 expected checksum values in a parametrized test.Reasoning
The base64 strings are 20- and 32-byte digests (Sha1/Sha256 values) paired with checksum class names in a parametrized test table. They are expected checksum outputs, not hidden code or payloads.
-
, , ), ]likely benign Base64-encoded SHA-512 expected checksum value in a parametrized test.Reasoning
The 88-character base64 string decodes to a 64-byte SHA-512 digest, and it is the expected value paired with Sha512Checksum in the same test table. This is ordinary test data.
-
= =likely benign Base64 pagination token fixture that encodes a JSON structure, used in a paginator test.Reasoning
The string decodes to JSON such as {"boto_encoded_keys": [["foo"]], "foo": "YmFy"}, which is a pagination token encoding format. The test asserts the decoded value, so this is a fixture for the paginator's token round-trip.
-
=likely benign Multi-part base64 pagination token fixture in a paginator test.Reasoning
This is a concatenated base64-encoded pagination token that decodes to nested JSON with encoded-key metadata. The surrounding test asserts the decoded result, which matches normal paginator test coverage.
-
=likely benign Base64 pagination token fixture for a nested-key paginator test.Reasoning
The concatenated base64 string is a pagination token that decodes to JSON with boto-encoded keys, and the test checks the decoded structure. It is test input for the paginator, not a payload.
-
) =likely benign Continuation of a base64 pagination token fixture in a paginator test.Reasoning
This is the continuation of the same base64 pagination token fixture, with the expected decoded dictionary given right after. It is a standard round-trip test case.
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.
&&