chore(iast): bytesio, stringio and read aspects

[gnufede]

Code Security: Basic propagation through StringIO/BytesIO objects, and read() calls to them.

Checklist

• PR author has checked that all the criteria below are met
• The PR description includes an overview of the change
• The PR description articulates the motivation for the change
• The change includes tests OR the PR description describes a testing strategy
• The PR description notes risks associated with the change, if any
• Newly-added code is easy to change
• The change follows the library release note guidelines
• The change includes or references documentation updates if necessary
• Backport labels are set (if applicable)

Reviewer Checklist

• Reviewer has checked that all the criteria below are met
• Title is accurate
• All changes are related to the pull request's stated goal
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Newly-added code is easy to change
• Release note makes sense to a user of the library
• If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
• Backport labels are set in a manner that is consistent with the release branch maintenance policy

[github-actions]

CODEOWNERS have been resolved as:

tests/appsec/iast/fixtures/ast/io/function_bytesio.py                   @DataDog/asm-python
tests/appsec/iast/fixtures/ast/io/function_stringio.py                  @DataDog/asm-python
tests/appsec/iast/fixtures/ast/io/module_bytesio.py                     @DataDog/asm-python
tests/appsec/iast/fixtures/ast/io/module_read.py                        @DataDog/asm-python
tests/appsec/iast/fixtures/ast/io/module_stringio.py                    @DataDog/asm-python
benchmarks/appsec_iast_aspects/config.yaml                              @DataDog/asm-python
benchmarks/bm/iast_fixtures/str_methods.py                              @DataDog/asm-python
ddtrace/appsec/_common_module_patches.py                                @DataDog/asm-python
ddtrace/appsec/_constants.py                                            @DataDog/asm-python
ddtrace/appsec/_iast/_ast/ast_patching.py                               @DataDog/asm-python
ddtrace/appsec/_iast/_ast/visitor.py                                    @DataDog/asm-python
ddtrace/appsec/_iast/_taint_tracking/Utils/StringUtils.cpp              @DataDog/asm-python
ddtrace/appsec/_iast/_taint_tracking/Utils/StringUtils.h                @DataDog/asm-python
ddtrace/appsec/_iast/_taint_tracking/__init__.py                        @DataDog/asm-python
ddtrace/appsec/_iast/_taint_tracking/aspects.py                         @DataDog/asm-python
tests/appsec/app.py                                                     @DataDog/asm-python
tests/appsec/iast/_ast/test_ast_patching.py                             @DataDog/asm-python
tests/appsec/iast/fixtures/propagation_path.py                          @DataDog/asm-python
tests/appsec/iast_memcheck/test_iast_mem_check.py                       @DataDog/asm-python
tests/appsec/integrations/test_flask_iast_patching.py                   @DataDog/asm-python

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: gnufede/iast-taint-bytesio
Commit report: d3fa59e
Test service: dd-trace-py

✅ 0 Failed, 1912 Passed, 217 Skipped, 864.57ms Total duration (18.46s time saved)

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-09-24 09:45:45

Comparing candidate commit 224ed21 in PR branch gnufede/iast-taint-bytesio with baseline commit e237d91 in branch main.

Some scenarios are present only in baseline or only in candidate runs. If you didn't create or remove some scenarios in your branch, this maybe a sign of crashed benchmarks 💥💥💥
Check Gitlab CI job log to find if any benchmark has crashed.

Scenarios present only in candidate:

• iast_aspects-aspect_no_iast_do_io_stringio_read
• iast_aspects-aspect_iast_do_io_stringio_read
• iast_aspects-aspect_no_iast_do_io_bytesio_read
• iast_aspects-aspect_iast_do_io_bytesio_read

Found 0 performance improvements and 0 performance regressions! Performance is the same for 365 metrics, 51 unstable metrics.