-
Notifications
You must be signed in to change notification settings - Fork 0
test: showcase semgrep integration and cost calculation #22
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| 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.""" | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🔒 Security | ❌ ERROR A sensitive password is hardcoded directly in the source code. Why this matters: Hardcoding sensitive information like passwords directly in the source code makes it easily discoverable and compromises the security of the application if the code is exposed. This violates the principle of secure configuration management and makes credential rotation difficult. |
||
| # 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" | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🔒 Security | ❌ ERROR The Why this matters: The application constructs a file path using unvalidated user input. This allows an attacker to manipulate the |
||
| 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) | ||
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
A sensitive API key is hardcoded directly in the source code.
Why this matters: Hardcoding sensitive information like API keys directly in the source code makes it easily discoverable and compromises the security of the application if the code is exposed. This violates the principle of secure configuration management and makes credential rotation difficult.