File size: 8,670 Bytes
90fc756
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
b83c8ad
 
 
 
 
90fc756
 
 
 
 
 
 
b83c8ad
 
 
 
 
90fc756
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
b83c8ad
 
 
 
 
90fc756
 
 
 
 
 
 
b83c8ad
 
 
 
 
90fc756
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
b83c8ad
 
 
 
 
 
90fc756
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
b83c8ad
 
 
 
 
90fc756
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
b83c8ad
 
 
 
 
90fc756
 
 
 
 
 
 
b83c8ad
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
90fc756
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
[
  {
    "task_id": "hard_001",
    "difficulty": "hard",
    "query": "SELECT * FROM users WHERE email = '${user_email}' AND password = '${password}';",
    "schema": {
      "users": {
        "id": "INT PRIMARY KEY",
        "email": "VARCHAR(255) UNIQUE",
        "password_hash": "VARCHAR(255)",
        "role": "VARCHAR(32)",
        "created_at": "TIMESTAMP"
      }
    },
    "context": "Authenticate a user during login.",
    "ground_truth_issues": [
      {
        "id": "hard_001_sql_injection",
        "category": "security",
        "description": "Interpolating user_email and password directly into the SQL creates a SQL injection vulnerability.",
        "severity": 1.0,
        "fix": "SELECT id, email, role FROM users WHERE email = ? AND password_hash = ?;",
        "keywords": [
          "sql injection", "interpolation", "user input", "parameterized", "security",
          "string concatenation", "prepared statement", "bind parameter",
          "unsanitized", "injection attack", "escape", "placeholder"
        ]
      },
      {
        "id": "hard_001_select_star_sensitive",
        "category": "security",
        "description": "SELECT * returns sensitive columns such as password hashes that the login flow does not need.",
        "severity": 0.4,
        "fix": "SELECT id, email, role FROM users WHERE email = ? AND password_hash = ?;",
        "keywords": [
          "select *", "sensitive columns", "password hash", "least privilege", "security",
          "over-exposure", "data leakage", "unnecessary columns",
          "password", "credential", "star query"
        ]
      }
    ],
    "max_steps": 6
  },
  {
    "task_id": "hard_002",
    "difficulty": "hard",
    "query": "SELECT id, email FROM customers UNION SELECT id, secret_value FROM admin_secrets;",
    "schema": {
      "customers": {
        "id": "INT PRIMARY KEY",
        "email": "VARCHAR(255)"
      },
      "admin_secrets": {
        "id": "INT PRIMARY KEY",
        "secret_value": "TEXT"
      }
    },
    "context": "Prepare a data export for a customer marketing campaign.",
    "ground_truth_issues": [
      {
        "id": "hard_002_secret_exfiltration",
        "category": "security",
        "description": "The UNION includes admin_secrets and leaks privileged data into a customer-facing export.",
        "severity": 0.95,
        "fix": "SELECT id, email FROM customers;",
        "keywords": [
          "union", "admin_secrets", "secret_value", "data leakage", "security",
          "exfiltration", "privileged data", "unauthorized access",
          "sensitive data", "data exposure", "information disclosure"
        ]
      },
      {
        "id": "hard_002_mixed_data_domains",
        "category": "logic",
        "description": "The query mixes unrelated datasets with incompatible semantics, producing an invalid export.",
        "severity": 0.45,
        "fix": "SELECT id, email FROM customers;",
        "keywords": [
          "union", "invalid export", "mixed dataset", "logic", "incompatible",
          "different tables", "semantic mismatch", "unrelated data",
          "data integrity", "domain mixing"
        ]
      }
    ],
    "max_steps": 6
  },
  {
    "task_id": "hard_003",
    "difficulty": "hard",
    "query": "SELECT c.id, c.full_name, c.ssn, c.email, t.subject FROM customers c JOIN support_tickets t ON t.customer_id = c.id WHERE t.status = 'open';",
    "schema": {
      "customers": {
        "id": "INT PRIMARY KEY",
        "full_name": "VARCHAR(255)",
        "ssn": "VARCHAR(32)",
        "email": "VARCHAR(255)"
      },
      "support_tickets": {
        "id": "INT PRIMARY KEY",
        "customer_id": "INT INDEX",
        "subject": "VARCHAR(255)",
        "status": "VARCHAR(32)"
      }
    },
    "context": "Show open support tickets to an agent dashboard.",
    "ground_truth_issues": [
      {
        "id": "hard_003_pii_leak",
        "category": "security",
        "description": "The dashboard query exposes SSNs even though the ticket workflow only needs identity and ticket context.",
        "severity": 0.9,
        "fix": "SELECT c.id, c.full_name, c.email, t.subject FROM customers c JOIN support_tickets t ON t.customer_id = c.id WHERE t.status = 'open';",
        "keywords": [
          "ssn", "pii", "sensitive data", "least privilege", "security",
          "social security", "personally identifiable", "data exposure",
          "unnecessary column", "information leakage", "over-fetching",
          "personal data"
        ]
      }
    ],
    "max_steps": 6
  },
  {
    "task_id": "hard_004",
    "difficulty": "hard",
    "query": "SELECT e1.department_id, e1.id, COUNT(e2.salary) + 1 AS salary_rank FROM employees e1 LEFT JOIN employees e2 ON e1.department_id = e2.department_id AND e2.salary > e1.salary GROUP BY e1.department_id, e1.id;",
    "schema": {
      "employees": {
        "id": "INT PRIMARY KEY",
        "department_id": "INT INDEX",
        "salary": "DECIMAL(10,2)"
      }
    },
    "context": "Rank employees by salary within each department.",
    "ground_truth_issues": [
      {
        "id": "hard_004_self_join_ranking",
        "category": "performance",
        "description": "The self-join ranking pattern is expensive and should use a window function such as DENSE_RANK().",
        "severity": 0.8,
        "fix": "SELECT department_id, id, DENSE_RANK() OVER (PARTITION BY department_id ORDER BY salary DESC) AS salary_rank FROM employees;",
        "keywords": [
          "self join", "window function", "dense_rank", "ranking", "performance",
          "self-join", "rank", "partition by", "over clause", "analytic function",
          "quadratic", "n squared"
        ]
      }
    ],
    "max_steps": 7
  },
  {
    "task_id": "hard_005",
    "difficulty": "hard",
    "query": "UPDATE accounts SET balance = balance - 100 WHERE user_id = 10; UPDATE accounts SET balance = balance + 100 WHERE user_id = 11;",
    "schema": {
      "accounts": {
        "user_id": "INT PRIMARY KEY",
        "balance": "DECIMAL(10,2)"
      }
    },
    "context": "Transfer money between two account balances.",
    "ground_truth_issues": [
      {
        "id": "hard_005_missing_transaction",
        "category": "security",
        "description": "The transfer uses two updates without a transaction, so a partial failure can corrupt balances.",
        "severity": 0.9,
        "fix": "BEGIN; UPDATE accounts SET balance = balance - 100 WHERE user_id = 10 AND balance >= 100; UPDATE accounts SET balance = balance + 100 WHERE user_id = 11; COMMIT;",
        "keywords": [
          "transaction", "partial failure", "atomic", "commit", "security",
          "begin", "rollback", "atomicity", "acid", "consistency",
          "two updates", "no transaction", "data corruption"
        ]
      },
      {
        "id": "hard_005_no_balance_guard",
        "category": "logic",
        "description": "The debit statement does not verify sufficient funds before subtracting the balance.",
        "severity": 0.55,
        "fix": "BEGIN; UPDATE accounts SET balance = balance - 100 WHERE user_id = 10 AND balance >= 100; UPDATE accounts SET balance = balance + 100 WHERE user_id = 11; COMMIT;",
        "keywords": [
          "balance guard", "insufficient funds", "where balance >=", "logic",
          "negative balance", "overdraft", "check balance", "guard clause",
          "minimum balance", "validation"
        ]
      }
    ],
    "max_steps": 7
  },
  {
    "task_id": "hard_006",
    "difficulty": "hard",
    "query": "UPDATE accounts SET balance = balance - 500 WHERE user_id = 42 AND balance >= 500;",
    "schema": {
      "accounts": {
        "user_id": "INT PRIMARY KEY",
        "balance": "DECIMAL(12,2)"
      }
    },
    "context": "Deduct $500 from user account for a withdrawal. Multiple withdrawal requests may arrive concurrently.",
    "ground_truth_issues": [
      {
        "id": "hard_006_race_condition",
        "category": "security",
        "description": "Without SELECT FOR UPDATE or proper transaction isolation, concurrent requests can pass the balance check simultaneously, allowing double-spending.",
        "severity": 0.9,
        "fix": "BEGIN; SELECT balance FROM accounts WHERE user_id = 42 FOR UPDATE; UPDATE accounts SET balance = balance - 500 WHERE user_id = 42 AND balance >= 500; COMMIT;",
        "keywords": [
          "race condition", "concurrent", "double spend", "for update",
          "transaction", "isolation", "lock", "toctou", "time of check",
          "atomicity", "concurrent requests", "locking", "serializable"
        ]
      }
    ],
    "max_steps": 7
  }
]