AST Security Linting & Dangerous Call Detection
Static AST linting detects dangerous patterns before code runs. A security visitor scans for prohibited identifiers (`eval`, `exec`, `__import__`, `open`), intercepting potential exploit vectors at compile time 🛡️.
import ast
BANNED = {"eval", "exec", "__import__", "open"}
class SecurityAuditor(ast.NodeVisitor):
def __init__(self):
self.violations = []
def visit_Call(self, node):
if isinstance(node.func, ast.Name) and node.func.id in BANNED:
self.violations.append(node.func.id)
self.generic_visit(node)
code = "eval('a + b'); print(100)"
auditor = SecurityAuditor()
auditor.visit(ast.parse(code))
print(f"Violations detected: {auditor.violations} 🛡️")
# 75. AST Security Linting & Dangerous Call Detection Static AST linting detects dangerous patterns before code runs. A security visitor scans for prohibited identifiers (`eval`, `exec`, `__import__`, `open`), intercepting potential exploit vectors at compile time 🛡️. ```python import ast BANNED = {"eval", "exec", "__import__", "open"} class SecurityAuditor(ast.NodeVisitor): def __init__(self): self.violations = [] def visit_Call(self, node): if isinstance(node.func, ast.Name) and node.func.id in BANNED: self.violations.append(node.func.id) self.generic_visit(node) code = "eval('a + b'); print(100)" auditor = SecurityAuditor() auditor.visit(ast.parse(code)) print(f"Violations detected: {auditor.violations} 🛡️") ``` Never rely solely on AST filtering to sandbox untrusted user code! Attackers can crawl `().__class__.__base__.__subclasses__()` to instantiate system types without naming them directly. True sandboxing requires Linux cgroups, WebAssembly, or isolated containers 🛡️! --- ### Question Why is AST static analysis alone insufficient to create a 100% impenetrable Python runtime sandbox? 🧠 - [ ] a. Dynamic introspection (`getattr`, `__subclasses__()`) can reconstruct banned references without using literal names 🛡️ - [ ] b. AST visitors can only inspect the first ten statements of any module - [ ] c. Python AST parser crashes when encountering recursive loops - [ ] d. Function calls inside list comprehensions are invisible to AST visitors --- ### Challenge Build an `ast.NodeVisitor` named `BlockEval` that records each `node.func.id` if it equals `'eval'`. Inspect `'eval(x); eval(y); abs(-5)'` and print the list of flagged calls. 🎯 <details> <summary>Solution</summary> ```python import ast class BlockEval(ast.NodeVisitor): def __init__(self): self.flagged = [] def visit_Call(self, node): if isinstance(node.func, ast.Name) and node.func.id == 'eval': self.flagged.append(node.func.id) self.generic_visit(node) b = BlockEval() b.visit(ast.parse('eval(x); eval(y); abs(-5)')) print(b.flagged) ``` </details>