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

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

Нейросеть18 июня 2026 11:01

That line looks like a classic time-based blind SQL injection payload:

  • 555-1; ends the prior statement (semicolon).
  • WAITFOR DELAY '0:0:15' instructs SQL Server to sleep for 15 seconds.
  • -- starts a comment, ignoring the rest of the query.

In short, an attacker could use this to infer information based on how long the server takes to respond, even if they can’t see query results.

Key exam points to know:

  • Types of SQL injection: in-band (e.g., union-based), inferential/time-based blind, and out-of-band.
  • How time-based blind SQLi works: inject a condition that, if true, triggers a delay (e.g., WAITFOR DELAY); measure response time to deduce data.
  • Common mitigations:
    • Use parameterized queries/prepared statements (do not concatenate user input into SQL).
    • Validate and sanitize input; apply least privilege on the DB account.
    • Avoid dynamic SQL built from user input; use stored procedures with parameters.
    • Use ORM safely and disable multiple-statement execution if possible.
    • Implement proper error handling and logging; use a WAF if appropriate.

If you want, I can give you a few practice questions or a quick quiz on SQL injection concepts.

555-1; waitfor delay '0:0:15' --
That line looks like a classic time-based blind SQL injection payload: - 555-1; ends the prior statement (semicolon). - WAITFOR DELAY '0:0:15' instructs SQL Server to sleep for 15 seconds. - -- starts a comment, ignoring the rest of the query. In short, an attacker could use this to infer information based on how long the server takes to respond, even if they can’t see query results. Key exam points to know: - Types of SQL injection: in-band (e.g., union-based), inferential/time-based blind, and out-of-band. - How time-based blind SQLi works: inject a condition that, if true, triggers a delay (e.g., WAITFOR DELAY); measure response time to deduce data. - Common mitigations: - Use parameterized queries/prepared statements (do not concatenate user input into SQL). - Validate and sanitize input; apply least privilege on the DB account. - Avoid dynamic SQL built from user input; use stored procedures with parameters. - Use ORM safely and disable multiple-statement execution if possible. - Implement proper error handling and logging; use a WAF if appropriate. If you want, I can give you a few practice questions or a quick quiz on SQL injection concepts.