사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/security-talent/bugskill-ai --skill bac-analyzer시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
BAC Analyzer - Passive Traffic Analysis for IDOR/BAC Vulnerabilities
Triggers
- "analyze traffic"
- "check for IDOR"
- "BAC analysis"
- "analyze HAR"
- "analyze Caido"
- "broken access control"
- "IDOR scan"
Description
Passive traffic analyzer that examines captured HTTP traffic (HAR, Caido JSON, Burp XML) to identify potential Broken Access Control (BAC) and Insecure Direct Object Reference (IDOR) vulnerabilities. Generates test cases and reports.
Input Formats
- HAR - HTTP Archive format (browser DevTools, Caido export)
- Caido JSON - Native Caido export format
- Burp XML - Burp Suite proxy history export
- Caido API - Direct pull from running Caido instance
Installation
# No external dependencies required - uses Python stdlib
chmod +x ~/.openclaw/workspace/skills/bac-analyzer/scripts/*.sh
chmod +x ~/.openclaw/workspace/skills/bac-analyzer/scripts/*.py
# Optional: Add to PATH
export PATH="$PATH:~/.openclaw/workspace/skills/bac-analyzer/scripts"Usage
Basic Analysis
# Analyze HAR file
./analyze.sh traffic.har
# Analyze Caido export
./analyze.sh caido-export.json
# Analyze Burp XML
./analyze.sh burp-history.xmlOptions
# Generate HTML report
./analyze.sh traffic.har -o report.html
# Tests only (no full report)
./analyze.sh traffic.har --tests-only
# JSON output
./analyze.sh traffic.har --json -o results.json
# Pull from Caido API (requires CAIDO_URL env var)
./analyze.sh --caido
# Verbose output
./analyze.sh traffic.har -vDirect Script Usage
# Parse specific format
python3 parse-har.py input.har -o parsed.json
# Detect IDs in parsed traffic
python3 detect-ids.py parsed.json -o ids.json
# Extract auth contexts
python3 extract-auth.py parsed.json -o auth.json
# Generate test cases
python3 generate-tests.py ids.json auth.json -o tests.json
# Generate HTML report
python3 report.py results.json -o report.htmlWhat It Detects
ID Patterns
- Integer IDs:
/users/123,?user_id=456 - UUIDs:
/docs/550e8400-e29b-41d4-a716-446655440000 - MongoDB ObjectIds:
/items/507f1f77bcf86cd799439011 - Base64 Encoded:
/api/dXNlcl8xMjM=(decodes touser_123) - Short Hashes:
/files/a1b2c3d4 - Composite IDs:
/org/123/user/456
High-Value Parameters
Automatically flags these sensitive parameters:
- userid, userId, uid, accountid, accountId
- orderid, orderId, transactionid
- documentid, fileid, invoice_id
- customerid, memberid, profile_id
- ssn, tin, dob (PII fields)
Auth Context
Extracts and groups requests by:
- Bearer tokens (Authorization header)
- Session cookies (JSESSIONID, PHPSESSID, etc.)
- API keys (X-API-Key, api_key parameter)
- Custom auth headers
Test Cases Generated
1. Auth-Switch Tests
Replace auth context A with context B on sensitive endpoints:
Original: GET /users/123 [Token: user_a_token]
Test: GET /users/123 [Token: user_b_token]2. Method Switching
Test alternate HTTP methods:
Original: GET /api/users/123
Tests: POST /api/users/123
PUT /api/users/123
DELETE /api/users/123
PATCH /api/users/1233. Parameter Pollution
Duplicate parameters with different values:
Original: ?user_id=123
Tests: ?user_id=123&user_id=456
?user_id[]=123&user_id[]=4564. 403 Bypass
When endpoint returns 403, generate bypass payloads:
/admin -> /admin/
/admin -> /admin%20
/admin -> /admin%00
/admin -> /ADMIN
/admin -> /admin/.
/admin -> //admin//
... (77+ bypass patterns)5. Actuator Checks
If Spring Boot detected, probe for actuator endpoints:
/actuator/health
/actuator/env
/actuator/heapdump
/actuator/loggers
...Output
Console Output
[*] Parsed 1,234 requests from traffic.har
[*] Detected 45 unique ID patterns
[*] Found 3 auth contexts
[*] Identified 89 high-risk endpoints
=== HIGH RISK ENDPOINTS ===
[CRITICAL] GET /api/users/{id}/profile
- Integer ID in path
- Contains PII fields in response
- 3 different auth contexts observed
[HIGH] POST /api/orders/{id}/cancel
- UUID in path
- State-changing operation
- No apparent auth check
=== GENERATED TEST CASES ===
Total: 234 test cases
- Auth-switch: 89
- Method switching: 67
- Parameter pollution: 45
- 403 bypass: 23
- Actuator checks: 10HTML Report
Interactive report with:
- Summary dashboard
- Risk-categorized endpoint list
- Copy-paste curl commands
- Filterable test cases
- Export to JSON/CSV
Integration with Research
Loads techniques from ~/.openclaw/workspace/data/idor-research/:
practitioner-techniques.json- Expert IDOR hunting patterns403-bypass-research.json- Bypass methodology research403bypass.md- URL manipulation payloadsactuators.md- Spring Boot actuator wordlist
Environment Variables
# Caido API (optional)
export CAIDO_URL="http://localhost:8080"
export CAIDO_API_KEY="your-api-key"
# Report output directory
export BAC_OUTPUT_DIR="/path/to/reports"Example Workflow
# 1. Export traffic from Caido/Burp/Browser
# 2. Run analysis
./analyze.sh traffic.har -o report.html
# 3. Review high-risk endpoints
# 4. Execute generated test cases
# 5. Verify findings manuallyNotes
- This is PASSIVE analysis - no requests sent to target
- Always verify findings manually before reporting
- Test cases are suggestions, not confirmed vulnerabilities
- Some patterns may produce false positives