PyPI / azure-core / 1.41.0
azure-core 1.41.0
- Source
- https://github.com/Azure/azure-sdk-for-python
- Tag scanned
azure-core_1.41.0- Directory
sdk/core/azure-core- Compared with
azure-core_1.40.0(0 signals introduced since)- Files
- 208 scanned, 12 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 16 info
- Scan time
- 12.6 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 14 of 14 warn and critical signals; 14 demoted to info.
- Disclude version
- 4.1.0
- Scanned (UTC)
- 2026-10-22 05:18
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
info
warn→ info by reviewdecoder-decompress-payloadsdk/core/azure-core/azure/core/pipeline/transport/_aiohttp.py:468:42= = = returnlikely benign Streaming HTTP response decompression in the aiohttp transport.Reasoning
The code decompresses an HTTP response body using zlib with wbits chosen from the Content-Encoding header (gzip or deflate). This is standard HTTP content decoding, not a hidden payload.
-
info
warn→ info by reviewdecoder-decompress-payloadsdk/core/azure-core/azure/core/utils/_pipeline_transport_rest_shared.py:410:24= = = = Truelikely benign Decompresses a response body according to its Content-Encoding header.Reasoning
Same pattern as the aiohttp transport: zlib decompression of a response body keyed on the Content-Encoding header. This is normal HTTP handling in an SDK.
-
info
critical→ info by reviewdynamic-executionsdk/core/azure-core/tests/async_tests/conftest.py:67:25# On linux, have to set shell=True = # Wait up to ~20s with backoff for Flask to start servinglikely benign Test fixture that starts a Flask server subprocess.Reasoning
A test fixture launches a local Flask server with shell=True so it can run a command built by the test harness. The command is test-controlled and nothing suggests attacker input reaches it.
-
info
unicode-mixed-scriptsdk/core/azure-core/tests/async_tests/test_rest_http_response_async.py:267:32= assert == == # assert latin-1 changes text decoding without changing encoding property -
info
warn→ info by reviewpayload-bytes-literalsdk/core/azure-core/tests/async_tests/test_universal_http_async.py:137:9, b b blikely benign Gzip-compressed response body embedded as a test fixture.Reasoning
The bytes literal begins with the gzip magic \x1f\x8b and encodes a gzip-compressed HTTP response body. Test fixtures commonly embed such data to exercise decompression paths.
-
info
warn→ info by reviewpayload-bytes-literalsdk/core/azure-core/tests/async_tests/test_universal_http_async.py:168:9, b b blikely benign Further chunk of a gzip-compressed test response fixture.Reasoning
A continuation of the same gzip-compressed test response fixture. It is test data for decompression handling, not a payload being executed.
-
# On linux, have to set shell=True = # Wait up to ~20s with backoff for Flask to start servinglikely benign Test fixture that starts a Flask server subprocess.Reasoning
Same test harness pattern as the async conftest: a local Flask server is started with shell=True using a test-controlled command.
-
: , : , # fake key suppressed in credscan : , }likely benign Fake SharedKey authorization value in a transport test.Reasoning
The base64-like value is a placeholder SharedKey credential in a test request. The line is explicitly annotated as a fake key suppressed in credscan.
-
b b # fake key suppressed in credscan b blikely benign Fake SharedKey authorization header in a transport test.Reasoning
The same placeholder SharedKey credential appears in a raw bytes request fixture and is annotated as fake for credscan.
-
info
warn→ info by reviewencoding-base64sdk/core/azure-core/tests/test_rest_http_request.py:376:53: , : , # fake key suppressed in credscan : , }likely benign Fake SharedKey authorization value in a REST request test.Reasoning
The same annotated placeholder SharedKey value appears in a REST request test. It is a fake credential, not a live secret.
-
info
warn→ info by reviewencoding-base64sdk/core/azure-core/tests/test_rest_http_request.py:388:52b b # fake key suppressed in credscan b blikely benign Fake SharedKey authorization header in a REST request test.Reasoning
This is the same annotated placeholder SharedKey header in a bytes fixture for a REST request test.
-
= assert == == # assert latin-1 changes text decoding without changing encoding property -
=likely benign Base64url-encoded claims value in a WWW-Authenticate test header.Reasoning
The base64-like segment is a claims parameter in an OAuth WWW-Authenticate challenge, which is a standard encoded JSON structure in auth error responses. It is test data for parsing those headers.
-
== )likely benign Base64-encoded OAuth claims JSON used as an expected value in a unit test.Reasoning
The raw pass flagged a base64 string in a test assertion. It decodes to a JSON claims object (access_token with nbf and xms_caeerror values), which is the expected OAuth claims-challenge fixture for the test. The file is a test and the blob is plain data with no execution or hidden payload. This is a legitimate test fixture, and the raw pass is known to be noisy.
-
/==likely benign Base64 OAuth claims parameter embedded in a test's WWW-Authenticate header string.Reasoning
The same base64 claims blob appears as a claims parameter inside a WWW-Authenticate header string in a test. It decodes to the same benign JSON claims fixture. No code execution, decoding pipeline, or concealed behavior is present, so this is a normal test value.
-
== )likely benign Repeated base64-encoded OAuth claims JSON used as an expected value in a unit test.Reasoning
This is a duplicate of the first finding: the identical base64 claims blob is used as an expected value in another assertion in the test file. It decodes to a benign claims JSON fixture and shows no sign of obfuscation or 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.
&&