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
- 11.1 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 14 of 14 warn and critical signals; 14 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-14 18:47
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 Library code decompressing HTTP response bodies based on Content-Encoding.Reasoning
Standard HTTP response decompression for gzip/deflate content-encoding using zlib with wbits set from the Content-Encoding header. This is normal library behavior, not an embedded payload being executed.
-
info
warn→ info by reviewdecoder-decompress-payloadsdk/core/azure-core/azure/core/utils/_pipeline_transport_rest_shared.py:410:24= = = = Truelikely benign HTTP response content decompression in azure-core shared transport utilities.Reasoning
Same pattern as the aiohttp transport: zlib decompression of HTTP response content according to Content-Encoding. Expected behavior for an HTTP client library.
-
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 starting a local Flask server subprocess.Reasoning
Test fixture launching a Flask test server with shell=True on Linux; the command is built locally by the test harness. Test infrastructure, not an attack, though shell=True with a variable command is worth a note.
-
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 fixture bytes for testing HTTP response decoding.Reasoning
Bytes literal is a gzip stream (starts with \x1f\x8b) used as a mocked HTTP response body to test decompression. Test fixture data, legitimate.
-
info
warn→ info by reviewpayload-bytes-literalsdk/core/azure-core/tests/async_tests/test_universal_http_async.py:168:9, b b blikely benign Additional gzip-compressed fixture bytes for decoding tests.Reasoning
Continuation of the same gzip test fixture payload used to mock a compressed HTTP response. Legitimate test data.
-
# On linux, have to set shell=True = # Wait up to ~20s with backoff for Flask to start servinglikely benign Test fixture starting a local Flask server subprocess.Reasoning
Same test server launcher as the async conftest, starting Flask with shell=True and a locally constructed command. Test harness code.
-
: , : , # fake key suppressed in credscan : , }likely benign Fake Azure SharedKey authorization value in a unit test.Reasoning
The string is a fake SharedKey Authorization header in a test, explicitly annotated as a fake key suppressed in credscan. Not a real credential or obfuscated payload.
-
b b # fake key suppressed in credscan b blikely benign Fake SharedKey authorization line in a test request fixture.Reasoning
Same fake SharedKey header value in a raw HTTP request fixture, annotated as a fake key. Benign test data.
-
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
Duplicate of the fake, credscan-suppressed SharedKey test header. Benign test data.
-
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 A fake SharedKey Authorization header value in a test request fixture.Reasoning
The raw pass flagged a base64-like string in an Authorization SharedKey header inside a test fixture. The inline comment says the key is fake and suppressed in credscan, and the surrounding lines are ordinary HTTP header construction. This is a test value, not obfuscation or a credential.
-
= assert == == # assert latin-1 changes text decoding without changing encoding property -
=likely benign A base64-encoded claims parameter in a test WWW-Authenticate header.Reasoning
The flagged blob is the base64 'claims' parameter of a WWW-Authenticate challenge in a unit test for Azure CAE (insufficient_claims). It decodes to a small JSON object (access_token nbf/xms_caeerror). This is expected protocol test data, not a payload or hidden code.
-
== )likely benign Expected base64 claims value in an assertion of a challenge-parsing test.Reasoning
The same base64 claims value is compared against the parser output in an assertion. It is test expectation data for a documented auth challenge format, with no execution or concealment involved.
-
/==likely benign Repeated base64 claims fixture within another test's WWW-Authenticate string.Reasoning
This is a repeated copy of the same base64 claims value embedded in a test header string for the CAE challenge scenario. It is fixture data that decodes to plain JSON, so it is not obfuscation.
-
== )likely benign Repeated expected base64 claims value in a challenge-parsing test assertion.Reasoning
This is another assertion repeating the same base64 claims test vector. The context is a unit test comparing parsed challenge parameters, so the finding is a false positive from the raw base64 heuristic.
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.
&&