Security: SQL Injection via String Formatting in SQLiteExtractor#904
Open
tomaioo wants to merge 1 commit into
Open
Security: SQL Injection via String Formatting in SQLiteExtractor#904tomaioo wants to merge 1 commit into
tomaioo wants to merge 1 commit into
Conversation
The `SQLiteExtractor.__call__` method constructs SQL queries using Python f-strings with direct string interpolation for table names and event lists. While `event_nos` uses `map(str, event_nos)` which converts to strings, the `_extractor_name` is used directly in the query without sanitization. If an attacker can control the extractor name, they could inject malicious SQL. More critically, the `event_list` is joined with commas but not parameterized, and the table name is directly interpolated. Signed-off-by: tomaioo <203048277+tomaioo@users.noreply.github.com>
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
Security: SQL Injection via String Formatting in SQLiteExtractor
Problem
Severity:
High| File:src/graphnet/data/extractors/internal/sqlite_extractor.py:L35The
SQLiteExtractor.__call__method constructs SQL queries using Python f-strings with direct string interpolation for table names and event lists. Whileevent_nosusesmap(str, event_nos)which converts to strings, the_extractor_nameis used directly in the query without sanitization. If an attacker can control the extractor name, they could inject malicious SQL. More critically, theevent_listis joined with commas but not parameterized, and the table name is directly interpolated.Solution
Use parameterized queries with
?placeholders instead of string formatting. For the IN clause, use a parameterized approach:query = f'SELECT * FROM {self._extractor_name} WHERE event_no IN ({','.join('?' * len(event_nos))})'and passevent_nosas parameters topd.read_sql_query. Also validate_extractor_nameagainst a whitelist of allowed table names.Changes
src/graphnet/data/extractors/internal/sqlite_extractor.py(modified)