objc-sql-injection-deep-audit

Audit Objective-C code for SQL injection risks in SQLite queries.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/jvalinsky/garazyk --skill objc-sql-injection-deep-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: objc-sql-injection-deep-audit
Source: https://github.com/jvalinsky/garazyk/tree/main/.opencode/skills/objc-sql-injection-deep-audit
Command: npx skills add https://github.com/jvalinsky/garazyk --skill objc-sql-injection-deep-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies and helps remediate SQL injection vulnerabilities within Objective-C codebases that interact with SQLite databases, going beyond simple pattern matching to analyze dynamic SQL construction and data flow.

Core Features & Use Cases

  • Vulnerability Detection: Pinpoints areas where user input might be improperly handled in SQL queries.
  • Code Analysis: Scans Objective-C files (.m, .mm, .h) for risky SQL patterns like string formatting and concatenation.
  • Use Case: When reviewing a feature that allows users to search or filter data stored in a local SQLite database, use this Skill to ensure that user-provided search terms cannot be used to execute arbitrary SQL commands.

Quick Start

Run the SQL injection scan script against the current directory and output results to /tmp/objc-sql-injection-deep-audit.

Frequently Asked Questions about objc-sql-injection-deep-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect SQL injection vulnerabilities in Objective-C SQLite code?

Detect SQL injection in Objective-C SQLite code by scanning .m, .mm, and .h files for dynamic SQL construction, risky string formatting, and concatenation of user input into queries. The audit identifies areas where user input is improperly handled and verifies parameterized query usage.

What risky Objective-C patterns lead to SQLite injection vulnerabilities?

Risky Objective-C patterns leading to SQLite injection include dynamic SQL construction via string formatting and concatenation of user input directly into queries. These patterns bypass parameterized query protections and allow arbitrary SQL command execution from user-provided search terms.

Can this audit verify if my Objective-C app uses parameterized queries correctly?

Yes, the audit verifies correct usage of parameterized queries and input sanitization in Objective-C code. It analyzes data flow into SQLite database interactions to ensure user-provided search terms cannot execute arbitrary SQL commands.

How do I run a security audit for SQL injection on my Objective-C codebase?

Run the SQL injection scan script against your current directory to audit the Objective-C codebase. The scan outputs vulnerability detection results to a designated temporary directory, pinpointing areas where user input is improperly handled in SQLite queries.

What's the best way to secure user search input in local SQLite databases on iOS?

Secure user search input in local SQLite databases by auditing Objective-C code for dynamic SQL construction and ensuring all user-provided terms use parameterized queries. Deep code analysis verifies data flow to prevent arbitrary SQL command execution.

Does this SQL injection audit catch vulnerabilities beyond simple pattern matching?

Yes, the audit goes beyond simple pattern matching by analyzing data flow and dynamic SQL construction in Objective-C files. It pinpoints vulnerabilities associated with string formatting, concatenation, and improper handling of user input in SQLite database interactions.