Vulnerability Scanner
Think like an attacker, defend like an expert. 2025 threat landscape awareness.
🔧 Runtime Scripts
Execute for automated validation:
| Script |
Purpose |
Usage |
cardume-security-scan (wraps scripts/security_scan.py) |
Validate security principles applied |
cardume-security-scan <project_path> |
📋 Reference Files
| File |
Purpose |
| checklists.md |
OWASP Top 10, Auth, API, Data protection checklists |
1. Security Expert Mindset
Core Principles
| Principle |
Application |
| Assume Breach |
Design as if attacker already inside |
| Zero Trust |
Never trust, always verify |
| Defense in Depth |
Multiple layers, no single point |
| Least Privilege |
Minimum required access only |
| Fail Secure |
On error, deny access |
Threat Modeling Questions
Before scanning, ask:
- What are we protecting? (Assets)
- Who would attack? (Threat actors)
- How would they attack? (Attack vectors)
- What's the impact? (Business risk)
2. OWASP Top 10:2025
Risk Categories
| Rank |
Category |
Think About |
| A01 |
Broken Access Control |
Who can access what? IDOR, SSRF |
| A02 |
Security Misconfiguration |
Defaults, headers, exposed services |
| A03 |
Software Supply Chain 🆕 |
Dependencies, CI/CD, build integrity |
| A04 |
Cryptographic Failures |
Weak crypto, exposed secrets |
| A05 |
Injection |
User input → system commands |
| A06 |
Insecure Design |
Flawed architecture |
| A07 |
Authentication Failures |
Session, credential management |
| A08 |
Integrity Failures |
Unsigned updates, tampered data |
| A09 |
Logging & Alerting |
Blind spots, no monitoring |
| A10 |
Exceptional Conditions 🆕 |
Error handling, fail-open states |
2025 Key Changes
2021 → 2025 Shifts:
├── SSRF merged into A01 (Access Control)
├── A02 elevated (Cloud/Container configs)
├── A03 NEW: Supply Chain (major focus)
├── A10 NEW: Exceptional Conditions
└── Focus shift: Root causes > Symptoms
3. Supply Chain Security (A03)
Attack Surface
| Vector |
Risk |
Question to Ask |
| Dependencies |
Malicious packages |
Do we audit new deps? |
| Lock files |
Integrity attacks |
Are they committed? |
| Build pipeline |
CI/CD compromise |
Who can modify? |
| Registry |
Typosquatting |
Verified sources? |
Defense Principles
- Verify package integrity (checksums)
- Pin versions, audit updates
- Use private registries for critical deps
- Sign and verify artifacts
4. Attack Surface Mapping
What to Map
| Category |
Elements |
| Entry Points |
APIs, forms, file uploads |
| Data Flows |
Input → Process → Output |
| Trust Boundaries |
Where auth/authz checked |
| Assets |
Secrets, PII, business data |
Prioritization Matrix
Risk = Likelihood × Impact
High Impact + High Likelihood → CRITICAL
High Impact + Low Likelihood → HIGH
Low Impact + High Likelihood → MEDIUM
Low Impact + Low Likelihood → LOW
5. Risk Prioritization
CVSS + Context
| Factor |
Weight |
Question |
| CVSS Score |
Base severity |
How severe is the vuln? |
| EPSS Score |
Exploit likelihood |
Is it being exploited? |
| Asset Value |
Business context |
What's at risk? |
| Exposure |
Attack surface |
Internet-facing? |
Prioritization Decision Tree
Is it actively exploited (EPSS >0.5)?
├── YES → CRITICAL: Immediate action
└── NO → Check CVSS
├── CVSS ≥9.0 → HIGH
├── CVSS 7.0-8.9 → Consider asset value
└── CVSS <7.0 → Schedule for later
6. Exceptional Conditions (A10 - New)
Fail-Open vs Fail-Closed
| Scenario |
Fail-Open (BAD) |
Fail-Closed (GOOD) |
| Auth error |
Allow access |
Deny access |
| Parsing fails |
Accept input |
Reject input |
| Timeout |
Retry forever |
Limit + abort |
What to Check
- Exception handlers that catch-all and ignore
- Missing error handling on security operations
- Race conditions in auth/authz
- Resource exhaustion scenarios
7. Scanning Methodology
Phase-Based Approach
1. RECONNAISSANCE
└── Understand the target
├── Technology stack
├── Entry points
└── Data flows
2. DISCOVERY
└── Identify potential issues
├── Configuration review
├── Dependency analysis
└── Code pattern search
3. ANALYSIS
└── Validate and prioritize
├── False positive elimination
├── Risk scoring
└── Attack chain mapping
4. REPORTING
└── Actionable findings
├── Clear reproduction steps
├── Business impact
└── Remediation guidance
8. Code Pattern Analysis
High-Risk Patterns
| Pattern |
Risk |
Look For |
| String concat in queries |
Injection |
"SELECT * FROM " + user_input |
| Dynamic code execution |
RCE |
eval(), exec(), Function() |
| Unsafe deserialization |
RCE |
pickle.loads(), unserialize() |
| Path manipulation |
Traversal |
User input in file paths |
| Disabled security |
Various |
verify=False, --insecure |
Secret Patterns
| Type |
Indicators |
| API Keys |
api_key, apikey, high entropy |
| Tokens |
token, bearer, jwt |
| Credentials |
password, secret, key |
| Cloud |
AWS_, AZURE_, GCP_ prefixes |
9. Cloud Security Considerations
Shared Responsibility
| Layer |
You Own |
Provider Owns |
| Data |
✅ |
❌ |
| Application |
✅ |
❌ |
| OS/Runtime |
Depends |
Depends |
| Infrastructure |
❌ |
✅ |
Cloud-Specific Checks
- IAM: Least privilege applied?
- Storage: Public buckets?
- Network: Security groups tightened?
- Secrets: Using secrets manager?
10. Anti-Patterns
| ❌ Don't |
✅ Do |
| Scan without understanding |
Map attack surface first |
| Alert on every CVE |
Prioritize by exploitability + asset |
| Ignore false positives |
Maintain verified baseline |
| Fix symptoms only |
Address root causes |
| Scan once before deploy |
Continuous scanning |
| Trust third-party deps blindly |
Verify integrity, audit code |
11. Reporting Principles
Finding Structure
Each finding should answer:
- What? - Clear vulnerability description
- Where? - Exact location (file, line, endpoint)
- Why? - Root cause explanation
- Impact? - Business consequence
- How to fix? - Specific remediation
Severity Classification
| Severity |
Criteria |
| Critical |
RCE, auth bypass, mass data exposure |
| High |
Data exposure, privilege escalation |
| Medium |
Limited scope, requires conditions |
| Low |
Informational, best practice |
Remember: Vulnerability scanning finds issues. Expert thinking prioritizes what matters. Always ask: "What would an attacker do with this?"
1---2name: vulnerability-scanner3description: "OWASP Top 10, supply chain and attack surface analysis with an automated scan. Use when auditing code or dependencies for vulnerabilities."4allowed-tools: Read Glob Grep Bash5compatibility: "Claude Code with the Cardume plugins (uses cardume-* commands, subagents or plugin paths); the guidance itself is portable."6metadata:7 source: https://skillmd.com/skills/jeffersonvalente/vulnerability-scanner8---910# Vulnerability Scanner1112> Think like an attacker, defend like an expert. 2025 threat landscape awareness.1314## 🔧 Runtime Scripts1516**Execute for automated validation:**1718| Script | Purpose | Usage |19|--------|---------|-------|20| `cardume-security-scan` (wraps `scripts/security_scan.py`) | Validate security principles applied | `cardume-security-scan <project_path>` |2122## 📋 Reference Files2324| File | Purpose |25|------|---------|26| [checklists.md](checklists.md) | OWASP Top 10, Auth, API, Data protection checklists |2728---2930## 1. Security Expert Mindset3132### Core Principles3334| Principle | Application |35|-----------|-------------|36| **Assume Breach** | Design as if attacker already inside |37| **Zero Trust** | Never trust, always verify |38| **Defense in Depth** | Multiple layers, no single point |39| **Least Privilege** | Minimum required access only |40| **Fail Secure** | On error, deny access |4142### Threat Modeling Questions4344Before scanning, ask:451. What are we protecting? (Assets)462. Who would attack? (Threat actors)473. How would they attack? (Attack vectors)484. What's the impact? (Business risk)4950---5152## 2. OWASP Top 10:20255354### Risk Categories5556| Rank | Category | Think About |57|------|----------|-------------|58| **A01** | Broken Access Control | Who can access what? IDOR, SSRF |59| **A02** | Security Misconfiguration | Defaults, headers, exposed services |60| **A03** | Software Supply Chain 🆕 | Dependencies, CI/CD, build integrity |61| **A04** | Cryptographic Failures | Weak crypto, exposed secrets |62| **A05** | Injection | User input → system commands |63| **A06** | Insecure Design | Flawed architecture |64| **A07** | Authentication Failures | Session, credential management |65| **A08** | Integrity Failures | Unsigned updates, tampered data |66| **A09** | Logging & Alerting | Blind spots, no monitoring |67| **A10** | Exceptional Conditions 🆕 | Error handling, fail-open states |6869### 2025 Key Changes7071```722021 → 2025 Shifts:73├── SSRF merged into A01 (Access Control)74├── A02 elevated (Cloud/Container configs)75├── A03 NEW: Supply Chain (major focus)76├── A10 NEW: Exceptional Conditions77└── Focus shift: Root causes > Symptoms78```7980---8182## 3. Supply Chain Security (A03)8384### Attack Surface8586| Vector | Risk | Question to Ask |87|--------|------|-----------------|88| **Dependencies** | Malicious packages | Do we audit new deps? |89| **Lock files** | Integrity attacks | Are they committed? |90| **Build pipeline** | CI/CD compromise | Who can modify? |91| **Registry** | Typosquatting | Verified sources? |9293### Defense Principles9495- Verify package integrity (checksums)96- Pin versions, audit updates97- Use private registries for critical deps98- Sign and verify artifacts99100---101102## 4. Attack Surface Mapping103104### What to Map105106| Category | Elements |107|----------|----------|108| **Entry Points** | APIs, forms, file uploads |109| **Data Flows** | Input → Process → Output |110| **Trust Boundaries** | Where auth/authz checked |111| **Assets** | Secrets, PII, business data |112113### Prioritization Matrix114115```116Risk = Likelihood × Impact117118High Impact + High Likelihood → CRITICAL119High Impact + Low Likelihood → HIGH120Low Impact + High Likelihood → MEDIUM121Low Impact + Low Likelihood → LOW122```123124---125126## 5. Risk Prioritization127128### CVSS + Context129130| Factor | Weight | Question |131|--------|--------|----------|132| **CVSS Score** | Base severity | How severe is the vuln? |133| **EPSS Score** | Exploit likelihood | Is it being exploited? |134| **Asset Value** | Business context | What's at risk? |135| **Exposure** | Attack surface | Internet-facing? |136137### Prioritization Decision Tree138139```140Is it actively exploited (EPSS >0.5)?141├── YES → CRITICAL: Immediate action142└── NO → Check CVSS143 ├── CVSS ≥9.0 → HIGH144 ├── CVSS 7.0-8.9 → Consider asset value145 └── CVSS <7.0 → Schedule for later146```147148---149150## 6. Exceptional Conditions (A10 - New)151152### Fail-Open vs Fail-Closed153154| Scenario | Fail-Open (BAD) | Fail-Closed (GOOD) |155|----------|-----------------|---------------------|156| Auth error | Allow access | Deny access |157| Parsing fails | Accept input | Reject input |158| Timeout | Retry forever | Limit + abort |159160### What to Check161162- Exception handlers that catch-all and ignore163- Missing error handling on security operations164- Race conditions in auth/authz165- Resource exhaustion scenarios166167---168169## 7. Scanning Methodology170171### Phase-Based Approach172173```1741. RECONNAISSANCE175 └── Understand the target176 ├── Technology stack177 ├── Entry points178 └── Data flows1791802. DISCOVERY181 └── Identify potential issues182 ├── Configuration review183 ├── Dependency analysis184 └── Code pattern search1851863. ANALYSIS187 └── Validate and prioritize188 ├── False positive elimination189 ├── Risk scoring190 └── Attack chain mapping1911924. REPORTING193 └── Actionable findings194 ├── Clear reproduction steps195 ├── Business impact196 └── Remediation guidance197```198199---200201## 8. Code Pattern Analysis202203### High-Risk Patterns204205| Pattern | Risk | Look For |206|---------|------|----------|207| **String concat in queries** | Injection | `"SELECT * FROM " + user_input` |208| **Dynamic code execution** | RCE | `eval()`, `exec()`, `Function()` |209| **Unsafe deserialization** | RCE | `pickle.loads()`, `unserialize()` |210| **Path manipulation** | Traversal | User input in file paths |211| **Disabled security** | Various | `verify=False`, `--insecure` |212213### Secret Patterns214215| Type | Indicators |216|------|-----------|217| API Keys | `api_key`, `apikey`, high entropy |218| Tokens | `token`, `bearer`, `jwt` |219| Credentials | `password`, `secret`, `key` |220| Cloud | `AWS_`, `AZURE_`, `GCP_` prefixes |221222---223224## 9. Cloud Security Considerations225226### Shared Responsibility227228| Layer | You Own | Provider Owns |229|-------|---------|---------------|230| Data | ✅ | ❌ |231| Application | ✅ | ❌ |232| OS/Runtime | Depends | Depends |233| Infrastructure | ❌ | ✅ |234235### Cloud-Specific Checks236237- IAM: Least privilege applied?238- Storage: Public buckets?239- Network: Security groups tightened?240- Secrets: Using secrets manager?241242---243244## 10. Anti-Patterns245246| ❌ Don't | ✅ Do |247|----------|-------|248| Scan without understanding | Map attack surface first |249| Alert on every CVE | Prioritize by exploitability + asset |250| Ignore false positives | Maintain verified baseline |251| Fix symptoms only | Address root causes |252| Scan once before deploy | Continuous scanning |253| Trust third-party deps blindly | Verify integrity, audit code |254255---256257## 11. Reporting Principles258259### Finding Structure260261Each finding should answer:2621. **What?** - Clear vulnerability description2632. **Where?** - Exact location (file, line, endpoint)2643. **Why?** - Root cause explanation2654. **Impact?** - Business consequence2665. **How to fix?** - Specific remediation267268### Severity Classification269270| Severity | Criteria |271|----------|----------|272| **Critical** | RCE, auth bypass, mass data exposure |273| **High** | Data exposure, privilege escalation |274| **Medium** | Limited scope, requires conditions |275| **Low** | Informational, best practice |276277---278279> **Remember:** Vulnerability scanning finds issues. Expert thinking prioritizes what matters. Always ask: "What would an attacker do with this?"