Repository navigation
chore: release 0.11.0 - #154
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 0.11.0 adds one change, #152.
code-injection(Detection: a code-injection rule for attacker input reaching eval, exec and other CODE sinks #152). The new rule reports attacker input that reaches the codeevalorexecruns, with the same verdicts as the other taint rules. Theevalandexecsinks now read the code argument only: the globals and locals passed with it are data.dangerous-evalstill reports every call toevalorexec. The regression corpus gains three findings, each reviewed as a true positive.The Enterprise
templatestable needs this release. It treats Jinja2, Flask and Mako template sources asCODEsinks (CoreTrace-Entreprise/coretrace-python-analyzer-plugins#3), and without this rule those sinks report nothing.Changes in this PR
pyproject.toml,coretrace_python.__version__, the release test, and the three version examples of the usage guide: the JSON report, itstool.components, and the VEXtooling.CHANGELOG.md: the Unreleased section is dated as 0.11.0. No entry changed.Verification
pytest: 1122 passed (buildinstalled, so the wheel tests run too).pytest -m regressionunder Python 3.12: 19 passed.ruff checkon the tracked files andmypy: clean.Tag
v0.11.0after merge to publish.