-
Notifications
You must be signed in to change notification settings - Fork 0
test: combined vulnerability demo for semgrep + LLM review #23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ramirobarraco
wants to merge
1
commit into
main
Choose a base branch
from
test/combined-vulnerabilities
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+69
−0
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,61 @@ | ||
| """Demo file with intentional vulnerabilities for semgrep showcase. | ||
|
|
||
| WARNING: This file contains intentionally vulnerable code for testing purposes. | ||
| DO NOT use any of these patterns in production code. | ||
| """ | ||
|
|
||
| import os | ||
| import pickle | ||
| import subprocess | ||
| import sqlite3 | ||
|
|
||
|
|
||
| def sql_injection_example(user_input: str) -> list: | ||
| """Vulnerable to SQL injection - user input directly in query.""" | ||
| conn = sqlite3.connect(":memory:") | ||
| cursor = conn.cursor() | ||
| # BAD: Direct string formatting with user input | ||
| query = f"SELECT * FROM users WHERE name = '{user_input}'" | ||
| cursor.execute(query) | ||
| return cursor.fetchall() | ||
|
|
||
|
|
||
| def command_injection_example(filename: str) -> str: | ||
| """Vulnerable to command injection via shell=True.""" | ||
| # BAD: User input passed to shell command | ||
| result = subprocess.run( | ||
| f"cat {filename}", | ||
| shell=True, | ||
| capture_output=True, | ||
| text=True, | ||
| ) | ||
| return result.stdout | ||
|
|
||
|
|
||
| def hardcoded_secret_example(): | ||
| """Contains hardcoded credentials - security risk.""" | ||
| # BAD: Hardcoded API key | ||
| api_key = "sk-1234567890abcdef1234567890abcdef" | ||
| password = "super_secret_password_123" | ||
| return {"api_key": api_key, "password": password} | ||
|
|
||
|
|
||
| def insecure_deserialization(data: bytes) -> object: | ||
| """Vulnerable to arbitrary code execution via pickle.""" | ||
| # BAD: Deserializing untrusted data with pickle | ||
| return pickle.loads(data) | ||
|
|
||
|
|
||
| def path_traversal_example(user_path: str) -> str: | ||
| """Vulnerable to path traversal attacks.""" | ||
| # BAD: No validation of user-supplied path | ||
| base_dir = "/var/data" | ||
| full_path = os.path.join(base_dir, user_path) | ||
| with open(full_path) as f: | ||
| return f.read() | ||
|
|
||
|
|
||
| def exec_user_code(code: str) -> None: | ||
| """Executes arbitrary user-supplied code.""" | ||
| # BAD: Executing untrusted code | ||
| exec(code) | ||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security | ❌ ERROR
Sensitive credentials, such as an API key and password, are hardcoded directly in the source code.
Why this matters: Embedding sensitive credentials directly into the source code makes them easily discoverable by anyone with access to the codebase, including version control history. This practice violates the principle of least privilege and significantly increases the risk of credential compromise, as these secrets are not managed securely and can be exposed in logs, build artifacts, or public repositories.