How do we test our API endpoints for command injection vulnerabilities using automated tools this afternoon?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How do we test our API endpoints for command injection vulnerabilities using automated tools this afternoon?
3 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (3)
Classes come from the query-classifier (a local Laya model). 3 of 3 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT3 real searches · gpt-6
OWASP ZAP API scan OpenAPI documentation passive active scanning API security testing Google ↗
Semgrep command injection detection rules documentation Google ↗
OWASP command injection prevention cheat sheet parameterized APIs Google ↗
- Official website and documentation · zaproxy.org
- Official website · portswigger.net
- Official website · 42crunch.com
- Official website · semgrep.dev
- OS Command Injection Defense · cheatsheetseries.owasp.org
- Injection Prevention · cheatsheetseries.owasp.org
Queries
3 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
OWASP ZAP API scan OpenAPI documentation passive active scanning API security testing OBSERVED | Google ↗ AI Mode ↗ | — | Instruction | — | — | 1x of 1 | |
Semgrep command injection detection rules documentation OBSERVED | Google ↗ AI Mode ↗ | — | Other / navigational | — | — | 1x of 1 | |
OWASP command injection prevention cheat sheet parameterized APIs OBSERVED | Google ↗ AI Mode ↗ | — | Instruction | — | — | 1x of 1 |