Новая Школа - онлайн-школа подготовки к ЕГЭ
Задача Задача №3622714
А
Аноним
18 июня 2026 10:27 · публичный вопрос
А
Аноним

555-1; waitfor delay '0:0:15' --

Ответ нейросети
18 июня 2026 10:27

It looks like a classic time-based blind SQL injection payload intended for SQL Server.

What it does, in brief:

  • waitfor delay '0:0:15' tells SQL Server to pause for 15 seconds.
  • The semicolon ends the preceding statement, and the -- comments out the rest of the original query.
  • If inserted into a vulnerable query, the attacker can observe a 15-second delay (or no delay) to infer information based on timing.

Why this matters for exams:

  • Time-based SQLi, especially in blind scenarios, is about extracting data by observing response times rather than visible results.
  • This payload is specific to SQL Server (T-SQL). Other DBs have different syntax for delaying or causing delays.

Defensive takeaways (exam-ready):

  • Always use parameterized queries/prepared statements. Do not concatenate user input into SQL strings.
  • Validate and sanitize inputs; apply least-privilege database accounts.
  • Avoid dynamic SQL; if dynamic SQL is necessary, use proper escaping and strong whitelisting where possible.
  • Use ORM features correctly and rely on bound parameters.
  • Implement robust error handling to avoid leaking database error details.
  • Monitor and log long-running queries; set alerts for unusual delays that could indicate injection attempts.
  • Use web/application firewalls and security testing in authorized lab environments (e.g., OWASP, DVWA-style labs) to practice safely.

quick exam-style question you can study:

  • Question: Explain how a payload like "...; WAITFOR DELAY '0:0:15' --" could be used in a SQL injection attack and why it is dangerous.
  • Answer: It ends the current statement, injects a time delay, and comments out the rest of the query. In a vulnerable app, this can cause the database to pause for a fixed time, revealing information via timing or simply helping the attacker confirm the injection point. It highlights the risk of unsanitized input and the need for parameterized queries and least privilege.

Would you like a concise defensive cheat sheet or a few practice quiz questions on SQL injection and other injection types?