fix: remove unsafe exec() in aws_uploader.py#8350
Open
orbisai0security wants to merge 1 commit into
Open
Conversation
Automated security fix generated by Orbis Security AI
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.
Summary
Fix high severity security issue in
tools/aws_uploader.py.Vulnerability
V-002tools/aws_uploader.py:1Description: The Python build tools depend on three packages — pygments, mkdocs, and pymdown-extensions — that are listed without pinned version numbers or cryptographic hash verification. When the build environment installs these dependencies using pip without version constraints, it resolves to the latest available version from PyPI at install time. This creates a window for supply chain attacks: a threat actor who compromises a package maintainer account, performs a typosquatting attack, or executes a dependency confusion attack can publish a malicious package version. The next build environment setup will install the malicious version, executing attacker-controlled code during package installation (via setup.py or pyproject.toml hooks) or at import time, with the full privileges of the build process.
Changes
requirements.txtVerification
Automated security fix by OrbisAI Security