Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
61 changes: 61 additions & 0 deletions src/vulnerable_demo.py
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():
Copy link
Copy Markdown

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.

"""Contains hardcoded credentials - security risk."""
Copy link
Copy Markdown

Choose a reason for hiding this comment

The 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"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔒 Security | ❌ ERROR

The user_path input is used to construct a file path without proper validation, leading to a path traversal vulnerability.

Why this matters: The application constructs a file path using unvalidated user input. This allows an attacker to manipulate the user_path to access arbitrary files or directories on the server's file system, potentially leading to information disclosure or unauthorized file modification. The underlying issue is the assumption that user_path will always represent a simple filename within the base_dir.

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)