[Precogs AI - Fix] SQL Injection (Critical) in sample-vuln/app.py#4
Open
sameer6pre wants to merge 1 commit intoPrecogs-fix-5kqi2b08from
Open
[Precogs AI - Fix] SQL Injection (Critical) in sample-vuln/app.py#4sameer6pre wants to merge 1 commit intoPrecogs-fix-5kqi2b08from
sameer6pre wants to merge 1 commit intoPrecogs-fix-5kqi2b08from
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
1 participant
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.
Precogs Auto-Fix
Vulnerability: SQL Injection
Severity: Critical
File:
sample-vuln/app.pyCWE: CWE-89
What was fixed
Primary: SQL Injection (CWE-89) — The get_user_by_name function constructs an SQL statement by interpolating the raw username into the query string using an f-string. This allows an attacker-controlled username to alter the SQL statement, enabling SQL injection. The cursor.execute call accepts the crafted SQL and executes it against the database without any parameterization or sanitization.
Also found: Hard-coded Secret (CWE-798) — A secret API_KEY value is hard-coded in source. Storing credentials or secrets in source code risks accidental disclosure (e.g., via version control, code leak) and makes rotation and environment-specific configuration difficult. An attacker discovering this key could authenticate to services or escalate privileges if that key is accepted by other systems.
This PR was automatically generated by Precogs AI. Review the changes before merging.