fix: the script accepts year and month values via ra... in...#848
Open
orbisai0security wants to merge 1 commit into
Open
fix: the script accepts year and month values via ra... in...#848orbisai0security wants to merge 1 commit into
orbisai0security wants to merge 1 commit into
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
cohorts/2025/workshops/dynamic_load_dlt.py.Vulnerability
V-003cohorts/2025/workshops/dynamic_load_dlt.py:43Description: The script accepts year and month values via raw input() calls and converts them with int() without any range validation or error handling. Values such as year=99999999 or month=99 are silently accepted and passed directly into downstream DLT pipeline logic. This can cause malformed date range construction, unexpected pipeline behavior, integer overflow in date arithmetic, or data corruption in DLT-managed datasets. A ValueError from non-numeric input will also produce an unhandled exception with a full traceback.
Changes
cohorts/2025/workshops/dynamic_load_dlt.pyVerification
Automated security fix by OrbisAI Security