Repository navigation
Expand file tree
/
Copy pathsample_report.html
More file actions
83 lines (83 loc) · 34.6 KB
/
Copy pathsample_report.html
File metadata and controls
83 lines (83 loc) · 34.6 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
<!doctype html>
<html lang="en"><head><meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>API Security Audit Report EXAMPLE000001</title>
<style>
:root{--bg:#f7f7f9;--fg:#1a1a1e;--card:#fff;--line:#e3e3e8;--muted:#6b7280}
@media(prefers-color-scheme:dark){:root{--bg:#16171b;--fg:#e7e7ea;--card:#1f2024;--line:#33343a;--muted:#9aa0a6}}
*{box-sizing:border-box}
body{margin:0;background:var(--bg);color:var(--fg);font:15px/1.5 system-ui,Segoe UI,Roboto,sans-serif;padding:24px}
h1{font-size:20px;margin:0 0 4px}
.sub{color:var(--muted);font-size:13px;margin-bottom:20px}
.cards{display:flex;gap:10px;flex-wrap:wrap;margin-bottom:20px}
.card{flex:1;min-width:90px;border:1px solid var(--line);border-top:3px solid var(--c);background:var(--card);
border-radius:8px;padding:12px;cursor:pointer;color:inherit;font:inherit;text-align:left}
.card.off{opacity:.35}
.card .n{display:block;font-size:24px;font-weight:700;color:var(--c)}
.card .l{font-size:12px;color:var(--muted)}
table{width:100%;border-collapse:collapse;background:var(--card);border:1px solid var(--line);border-radius:8px;overflow:hidden}
th,td{text-align:left;padding:10px 12px;border-bottom:1px solid var(--line);vertical-align:top;font-size:14px}
thead th{background:rgba(127,127,127,.08);font-size:12px;text-transform:uppercase;letter-spacing:.03em}
.pill{color:#fff;padding:2px 8px;border-radius:999px;font-size:12px;font-weight:600}
.desc{color:var(--muted);margin-top:4px}
.rec,.mv,.ev{margin-top:6px;font-size:13px}
.ev code{word-break:break-all}
.tgt{max-width:220px;overflow-wrap:anywhere}
.meta{margin-top:24px;font-size:13px;color:var(--muted)}
.meta table{max-width:560px}
footer{margin-top:20px;color:var(--muted);font-size:12px}
</style></head><body>
<h1>API Security Audit Report</h1>
<div class="sub">Audit <code>EXAMPLE000001</code> · 2026-01-01T00:00:00+00:00 · v0.1.0</div>
<div class="cards"><button class="card" data-sev="CRITICAL" style="--c:#b4232a"><span class="n">2</span><span class="l">CRITICAL</span></button><button class="card" data-sev="HIGH" style="--c:#d4691e"><span class="n">6</span><span class="l">HIGH</span></button><button class="card" data-sev="MEDIUM" style="--c:#b8860b"><span class="n">10</span><span class="l">MEDIUM</span></button><button class="card" data-sev="LOW" style="--c:#2a6fb4"><span class="n">15</span><span class="l">LOW</span></button><button class="card" data-sev="INFO" style="--c:#6b7280"><span class="n">5</span><span class="l">INFO</span></button></div>
<table><thead><tr><th>Severity</th><th>Status</th><th>Finding</th><th>Check / OWASP</th><th>Target</th></tr></thead>
<tbody id="tb"><tr data-sev="CRITICAL"><td><span class="pill" style="background:#b4232a">CRITICAL</span></td><td>confirmed<br><small>HIGH</small></td><td><strong>Broken Object Level Authorization: order #1 (user_a)</strong><div class="desc">Identity 'admin' successfully retrieved user_a's object (HTTP 200) and the owner-specific discriminator 'SECRET-ORDER-1' was present in the response.</div><div class="rec"><b>Remediation:</b> Enforce object-level ownership checks on every object access, server-side.</div><div class="ev"><b>Evidence:</b> <code>{"owner": {"name": "user_a", "role": "user", "anonymous": false, "headers": ["Authorization"]}, "attacker": {"name": "admin", "role": "admin", "anonymous": false, "headers": ["Authorization"]}, "status_code": 200, "discriminator_found": true, "occurrences": 1}</code></div></td><td><code>BOLA-CONFIRMED</code><br><small>API1:2023</small></td><td class="tgt"><code>https://api.lab.local/orders/1</code></td></tr>
<tr data-sev="CRITICAL"><td><span class="pill" style="background:#b4232a">CRITICAL</span></td><td>confirmed<br><small>HIGH</small></td><td><strong>JWT declares 'alg: none' (unsigned)</strong><div class="desc">The token's header declares the 'none' algorithm, meaning it carries no signature. If the server accepts such tokens, anyone can forge arbitrary claims. This is a structural fact about the token header.</div><div class="rec"><b>Remediation:</b> Reject 'none' server-side; pin an allow-list of strong algorithms.</div><div class="mv"><b>Manual verification:</b> Confirm the server actually accepts this token (vs. rejecting 'none').</div><div class="ev"><b>Evidence:</b> <code>{"alg": "none", "segments": 3, "occurrences": 1}</code></div></td><td><code>JWT-ALG-NONE</code><br><small>API2:2023</small></td><td class="tgt"><code></code></td></tr>
<tr data-sev="HIGH"><td><span class="pill" style="background:#d4691e">HIGH</span></td><td>confirmed<br><small>HIGH</small></td><td><strong>CORS reflects an arbitrary Origin</strong><div class="desc">The server reflected the attacker-supplied Origin 'https://evil.example.com' into Access-Control-Allow-Origin WITH credentials enabled, allowing cross-origin credentialed reads.</div><div class="rec"><b>Remediation:</b> Validate Origin against a strict allow-list; do not reflect arbitrary origins.</div><div class="mv"><b>Manual verification:</b> Confirm a sensitive, cookie-authenticated endpoint is reachable via this CORS policy.</div><div class="ev"><b>Evidence:</b> <code>{"reflected_origin": "https://evil.example.com", "access-control-allow-credentials": "true", "occurrences": 1}</code></div></td><td><code>CORS-ORIGIN-REFLECTION</code><br><small>API8:2023</small></td><td class="tgt"><code>https://api.lab.local/me</code></td></tr>
<tr data-sev="HIGH"><td><span class="pill" style="background:#d4691e">HIGH</span></td><td>confirmed<br><small>HIGH</small></td><td><strong>Possible AWS access key id in response</strong><div class="desc">The response from https://api.lab.local/debug/config contains 1 match(es) for 'AWS access key id'. Confirm whether this data should be returned to this caller and whether it is real (not seeded test data).</div><div class="rec"><b>Remediation:</b> Remove sensitive values from responses; return only authorised, minimal fields.</div><div class="mv"><b>Manual verification:</b> Inspect the raw response and confirm the value is a real secret/PII, not a fixture.</div><div class="ev"><b>Evidence:</b> <code>{"pattern": "AWS access key id", "count": 1, "sample": "AKI…LE (len=20)", "occurrences": 1}</code></div></td><td><code>LEAK-AWS-ACCESS-KEY-ID</code><br><small>API3:2023</small></td><td class="tgt"><code>https://api.lab.local/debug/config</code></td></tr>
<tr data-sev="HIGH"><td><span class="pill" style="background:#d4691e">HIGH</span></td><td>suspected<br><small>MEDIUM</small></td><td><strong>Protected route returned success without authentication</strong><div class="desc">A GET request to https://api.lab.local/me with no credentials returned HTTP 200. The route was declared as protected, so this may indicate missing authentication — but confirm the response actually contains protected data and is not a public placeholder.</div><div class="rec"><b>Remediation:</b> Require and verify authentication before serving this route.</div><div class="mv"><b>Manual verification:</b> Inspect the anonymous response body: does it expose data that should require login?</div><div class="ev"><b>Evidence:</b> <code>{"anonymous_status": 200, "body_length": 82, "occurrences": 1}</code></div></td><td><code>AUTH-ANON-ACCESS</code><br><small>API2:2023</small></td><td class="tgt"><code>https://api.lab.local/me</code></td></tr>
<tr data-sev="HIGH"><td><span class="pill" style="background:#d4691e">HIGH</span></td><td>suspected<br><small>MEDIUM</small></td><td><strong>Invalid credential accepted</strong><div class="desc">https://api.lab.local/orders/1 returned HTTP 200 when presented with a clearly invalid bearer token, while a different response was expected. The token may not be validated.</div><div class="rec"><b>Remediation:</b> Validate token signature, expiry and audience server-side.</div><div class="mv"><b>Manual verification:</b> Repeat with several malformed tokens; confirm the data returned is genuinely protected.</div><div class="ev"><b>Evidence:</b> <code>{"invalid_status": 200, "occurrences": 1}</code></div></td><td><code>AUTH-INVALID-TOKEN-ACCEPTED</code><br><small>API2:2023</small></td><td class="tgt"><code>https://api.lab.local/orders/1</code></td></tr>
<tr data-sev="HIGH"><td><span class="pill" style="background:#d4691e">HIGH</span></td><td>suspected<br><small>MEDIUM</small></td><td><strong>Low-privilege identity invoked privileged function: admin user listing</strong><div class="desc">'user_a' (role=user) received HTTP 200 on a route declared as privileged. A high-role baseline also succeeded, supporting that this is a real function.</div><div class="rec"><b>Remediation:</b> Enforce role checks at the function/endpoint level, server-side.</div><div class="mv"><b>Manual verification:</b> Confirm the action actually executed with low-role privileges (side effects).</div><div class="ev"><b>Evidence:</b> <code>{"low_role": {"name": "user_a", "role": "user", "anonymous": false, "headers": ["Authorization"]}, "status_code": 200, "occurrences": 1}</code></div></td><td><code>BFLA-ACCESS</code><br><small>API5:2023</small></td><td class="tgt"><code>GET https://api.lab.local/admin/users</code></td></tr>
<tr data-sev="HIGH"><td><span class="pill" style="background:#d4691e">HIGH</span></td><td>confirmed<br><small>MEDIUM</small></td><td><strong>Exposed Environment file: /.env</strong><div class="desc">/.env returned HTTP 200 (application/json). This path is reachable and should be reviewed for whether it belongs on this surface.</div><div class="rec"><b>Remediation:</b> Never serve dotfiles/VCS metadata; block /.env and /.git at the web server.</div><div class="mv"><b>Manual verification:</b> Open the path and confirm it exposes sensitive data/functionality.</div><div class="ev"><b>Evidence:</b> <code>{"status_code": 200, "content_type": "application/json", "catch_all_baseline": false, "occurrences": 1}</code></div></td><td><code>EXPOSURE-FILE</code><br><small>API8:2023</small></td><td class="tgt"><code>https://api.lab.local/.env</code></td></tr>
<tr data-sev="MEDIUM"><td><span class="pill" style="background:#b8860b">MEDIUM</span></td><td>suspected<br><small>HIGH</small></td><td><strong>Missing required security header: strict-transport-security</strong><div class="desc">The response is missing 'strict-transport-security'. APIs served over HTTPS should enforce HSTS to prevent downgrade.</div><div class="rec"><b>Remediation:</b> Set the 'strict-transport-security' header at the API gateway or application layer.</div><div class="ev"><b>Evidence:</b> <code>{"occurrences": 1}</code></div></td><td><code>CONFIG-MISSING-HEADER</code><br><small>API8:2023</small></td><td class="tgt"><code>https://api.lab.local</code></td></tr>
<tr data-sev="MEDIUM"><td><span class="pill" style="background:#b8860b">MEDIUM</span></td><td>confirmed<br><small>HIGH</small></td><td><strong>CORS allows the 'null' origin</strong><div class="desc">The server returns 'Access-Control-Allow-Origin: null', which can be forged by sandboxed documents.</div><div class="rec"><b>Remediation:</b> Do not allow the 'null' origin.</div><div class="ev"><b>Evidence:</b> <code>{"access-control-allow-credentials": "true", "occurrences": 1}</code></div></td><td><code>CORS-NULL-ORIGIN</code><br><small>API8:2023</small></td><td class="tgt"><code>https://api.lab.local/me</code></td></tr>
<tr data-sev="MEDIUM"><td><span class="pill" style="background:#b8860b">MEDIUM</span></td><td>suspected<br><small>MEDIUM</small></td><td><strong>Error response leaks technical details</strong><div class="desc">A request to a non-existent path returned a body containing stack-trace / debug markers: ['Traceback (most recent call last)', '/var/www/']. Verbose errors can reveal framework internals.</div><div class="rec"><b>Remediation:</b> Return generic error bodies in production; disable debug mode.</div><div class="ev"><b>Evidence:</b> <code>{"markers": ["Traceback (most recent call last)", "/var/www/"], "status_code": 404, "occurrences": 1}</code></div></td><td><code>CONFIG-ERROR-LEAK</code><br><small>API8:2023</small></td><td class="tgt"><code>https://api.lab.local/__apt_nonexistent_probe__</code></td></tr>
<tr data-sev="MEDIUM"><td><span class="pill" style="background:#b8860b">MEDIUM</span></td><td>suspected<br><small>MEDIUM</small></td><td><strong>Server error on malformed input: invalid_json</strong><div class="desc">Case 'invalid_json' (Syntactically invalid JSON) produced HTTP 500. Well-validated APIs reject malformed input with a 4xx, not a 5xx.</div><div class="rec"><b>Remediation:</b> Validate and reject malformed input early with a 4xx and a generic message.</div><div class="mv"><b>Manual verification:</b> Reproduce the case and inspect server logs for unhandled exceptions.</div><div class="ev"><b>Evidence:</b> <code>{"case": "invalid_json", "status_code": 500, "occurrences": 1}</code></div></td><td><code>INPUT-SERVER-ERROR</code><br><small>API8:2023</small></td><td class="tgt"><code>POST https://api.lab.local/items</code></td></tr>
<tr data-sev="MEDIUM"><td><span class="pill" style="background:#b8860b">MEDIUM</span></td><td>suspected<br><small>MEDIUM</small></td><td><strong>Verbose error leak on input case: invalid_json</strong><div class="desc">Case 'invalid_json' returned a body with trace markers ['Traceback (most recent call last)'].</div><div class="rec"><b>Remediation:</b> Disable verbose errors/debug mode in production.</div><div class="ev"><b>Evidence:</b> <code>{"case": "invalid_json", "markers": ["Traceback (most recent call last)"], "occurrences": 1}</code></div></td><td><code>INPUT-ERROR-LEAK</code><br><small>API8:2023</small></td><td class="tgt"><code>POST https://api.lab.local/items</code></td></tr>
<tr data-sev="MEDIUM"><td><span class="pill" style="background:#b8860b">MEDIUM</span></td><td>suspected<br><small>MEDIUM</small></td><td><strong>JWT has no expiry (exp) claim</strong><div class="desc">The token declares no 'exp'. A non-expiring token is dangerous if leaked.</div><div class="rec"><b>Remediation:</b> Always set a short 'exp'; use refresh tokens for longer sessions.</div><div class="ev"><b>Evidence:</b> <code>{"occurrences": 1}</code></div></td><td><code>JWT-NO-EXP</code><br><small>API2:2023</small></td><td class="tgt"><code></code></td></tr>
<tr data-sev="MEDIUM"><td><span class="pill" style="background:#b8860b">MEDIUM</span></td><td>confirmed<br><small>MEDIUM</small></td><td><strong>Exposed Spring Boot environment: /actuator/env</strong><div class="desc">/actuator/env returned HTTP 200 (application/json). This path is reachable and should be reviewed for whether it belongs on this surface.</div><div class="rec"><b>Remediation:</b> Secure or disable actuator endpoints in production; never expose /env.</div><div class="mv"><b>Manual verification:</b> Open the path and confirm it exposes sensitive data/functionality.</div><div class="ev"><b>Evidence:</b> <code>{"status_code": 200, "content_type": "application/json", "catch_all_baseline": false, "occurrences": 1}</code></div></td><td><code>EXPOSURE-ACTUATOR</code><br><small>API8:2023</small></td><td class="tgt"><code>https://api.lab.local/actuator/env</code></td></tr>
<tr data-sev="MEDIUM"><td><span class="pill" style="background:#b8860b">MEDIUM</span></td><td>suspected<br><small>LOW</small></td><td><strong>Anonymous and authenticated responses are indistinguishable</strong><div class="desc">Anonymous and authenticated requests returned the same status and similar size. Authentication may have no effect on this route, or the route is public.</div><div class="mv"><b>Manual verification:</b> Confirm whether this route is intended to be public.</div><div class="ev"><b>Evidence:</b> <code>{"anonymous_status": 200, "authenticated_status": 200, "identity": {"name": "user_a", "role": "user", "anonymous": false, "headers": ["Authorization"]}, "occurrences": 1}</code></div></td><td><code>AUTH-NO-DIFFERENCE</code><br><small>API2:2023</small></td><td class="tgt"><code>https://api.lab.local/me</code></td></tr>
<tr data-sev="MEDIUM"><td><span class="pill" style="background:#b8860b">MEDIUM</span></td><td>suspected<br><small>LOW</small></td><td><strong>Response exposes sensitive properties: https://api.lab.local/me</strong><div class="desc">The response for 'user_a' contains properties that are often sensitive: ['is_admin', 'password_hash', 'role']. Confirm whether this identity should receive these fields.</div><div class="rec"><b>Remediation:</b> Return only properties the caller is authorised to see (allow-list serialisers).</div><div class="mv"><b>Manual verification:</b> Check whether these fields are necessary for this consumer and role.</div><div class="ev"><b>Evidence:</b> <code>{"properties": ["is_admin", "password_hash", "role"], "identity": {"name": "user_a", "role": "user", "anonymous": false, "headers": ["Authorization"]}, "occurrences": 1}</code></div></td><td><code>BOPLA-EXCESSIVE-EXPOSURE</code><br><small>API3:2023</small></td><td class="tgt"><code>https://api.lab.local/me</code></td></tr>
<tr data-sev="MEDIUM"><td><span class="pill" style="background:#b8860b">MEDIUM</span></td><td>suspected<br><small>LOW</small></td><td><strong>JWT algorithm 'none' differs from expected 'RS256'</strong><div class="desc">The token uses a different algorithm than expected. Verify the server validates the algorithm explicitly.</div><div class="rec"><b>Remediation:</b> Pin the exact expected algorithm; never trust the token's 'alg' blindly.</div><div class="mv"><b>Manual verification:</b> Try presenting a token re-signed with the mismatched alg to the server.</div><div class="ev"><b>Evidence:</b> <code>{"alg": "none", "expected_alg": "RS256", "occurrences": 1}</code></div></td><td><code>JWT-ALG-MISMATCH</code><br><small>API2:2023</small></td><td class="tgt"><code></code></td></tr>
<tr data-sev="LOW"><td><span class="pill" style="background:#2a6fb4">LOW</span></td><td>suspected<br><small>HIGH</small></td><td><strong>Missing recommended security header: x-content-type-options</strong><div class="desc">The response is missing 'x-content-type-options'. Prevents MIME sniffing; cheap and safe to send on JSON APIs.</div><div class="rec"><b>Remediation:</b> Set the 'x-content-type-options' header at the API gateway or application layer.</div><div class="ev"><b>Evidence:</b> <code>{"occurrences": 1}</code></div></td><td><code>CONFIG-MISSING-HEADER</code><br><small>API8:2023</small></td><td class="tgt"><code>https://api.lab.local</code></td></tr>
<tr data-sev="LOW"><td><span class="pill" style="background:#2a6fb4">LOW</span></td><td>suspected<br><small>HIGH</small></td><td><strong>Missing recommended security header: cache-control</strong><div class="desc">The response is missing 'cache-control'. Sensitive API responses should not be cached by intermediaries.</div><div class="rec"><b>Remediation:</b> Set the 'cache-control' header at the API gateway or application layer.</div><div class="ev"><b>Evidence:</b> <code>{"occurrences": 1}</code></div></td><td><code>CONFIG-MISSING-HEADER</code><br><small>API8:2023</small></td><td class="tgt"><code>https://api.lab.local</code></td></tr>
<tr data-sev="LOW"><td><span class="pill" style="background:#2a6fb4">LOW</span></td><td>suspected<br><small>HIGH</small></td><td><strong>Information disclosure header present: server</strong><div class="desc">The 'server' header discloses software details: 'nginx/1.18.0 (Ubuntu)'.</div><div class="rec"><b>Remediation:</b> Strip the 'server' header at the edge.</div><div class="ev"><b>Evidence:</b> <code>{"occurrences": 1}</code></div></td><td><code>CONFIG-INFO-DISCLOSURE</code><br><small>API8:2023</small></td><td class="tgt"><code>https://api.lab.local</code></td></tr>
<tr data-sev="LOW"><td><span class="pill" style="background:#2a6fb4">LOW</span></td><td>suspected<br><small>HIGH</small></td><td><strong>Information disclosure header present: x-powered-by</strong><div class="desc">The 'x-powered-by' header discloses software details: 'Express'.</div><div class="rec"><b>Remediation:</b> Strip the 'x-powered-by' header at the edge.</div><div class="ev"><b>Evidence:</b> <code>{"occurrences": 1}</code></div></td><td><code>CONFIG-INFO-DISCLOSURE</code><br><small>API8:2023</small></td><td class="tgt"><code>https://api.lab.local</code></td></tr>
<tr data-sev="LOW"><td><span class="pill" style="background:#2a6fb4">LOW</span></td><td>informational<br><small>HIGH</small></td><td><strong>GraphQL introspection is enabled</strong><div class="desc">The endpoint answered an introspection query. Introspection exposes the full schema. This is often intentional (e.g. for developer tooling) — treat it as an observation and decide based on the API's exposure and sensitivity.</div><div class="rec"><b>Remediation:</b> Disable introspection on production, internet-facing endpoints if not required.</div><div class="mv"><b>Manual verification:</b> Decide whether schema disclosure is acceptable for this endpoint's audience.</div><div class="ev"><b>Evidence:</b> <code>{"introspection": true, "occurrences": 1}</code></div></td><td><code>GRAPHQL-INTROSPECTION</code><br><small>API8:2023, API9:2023</small></td><td class="tgt"><code>https://api.lab.local/graphql</code></td></tr>
<tr data-sev="LOW"><td><span class="pill" style="background:#2a6fb4">LOW</span></td><td>confirmed<br><small>HIGH</small></td><td><strong>Exposed OpenAPI document: /openapi.json</strong><div class="desc">/openapi.json returned HTTP 200 (application/json). This path is reachable and should be reviewed for whether it belongs on this surface.</div><div class="rec"><b>Remediation:</b> Decide whether public API docs are intended; restrict if the API is private.</div><div class="mv"><b>Manual verification:</b> Open the path and confirm it exposes sensitive data/functionality.</div><div class="ev"><b>Evidence:</b> <code>{"status_code": 200, "content_type": "application/json", "catch_all_baseline": false, "occurrences": 1}</code></div></td><td><code>EXPOSURE-DOCS</code><br><small>API9:2023</small></td><td class="tgt"><code>https://api.lab.local/openapi.json</code></td></tr>
<tr data-sev="LOW"><td><span class="pill" style="background:#2a6fb4">LOW</span></td><td>confirmed<br><small>HIGH</small></td><td><strong>Exposed GraphQL endpoint: /graphql</strong><div class="desc">/graphql returned HTTP 200 (application/json). This path is reachable and should be reviewed for whether it belongs on this surface.</div><div class="rec"><b>Remediation:</b> Decide whether public API docs are intended; restrict if the API is private.</div><div class="mv"><b>Manual verification:</b> Open the path and confirm it exposes sensitive data/functionality.</div><div class="ev"><b>Evidence:</b> <code>{"status_code": 200, "content_type": "application/json", "catch_all_baseline": false, "occurrences": 1}</code></div></td><td><code>EXPOSURE-DOCS</code><br><small>API9:2023</small></td><td class="tgt"><code>https://api.lab.local/graphql</code></td></tr>
<tr data-sev="LOW"><td><span class="pill" style="background:#2a6fb4">LOW</span></td><td>suspected<br><small>MEDIUM</small></td><td><strong>Server exposes technology/version banners</strong><div class="desc">Response headers reveal software/version hints that can aid an attacker in fingerprinting the stack: server='nginx/1.18.0 (Ubuntu)'; x-powered-by='Express'</div><div class="rec"><b>Remediation:</b> Remove or genericise Server/X-Powered-By style banners at the gateway.</div><div class="ev"><b>Evidence:</b> <code>{"headers": {"server": "nginx/1.18.0 (Ubuntu)", "x-powered-by": "Express"}, "occurrences": 1}</code></div></td><td><code>RECON-TECH-HINTS</code><br><small>API8:2023</small></td><td class="tgt"><code>https://api.lab.local</code></td></tr>
<tr data-sev="LOW"><td><span class="pill" style="background:#2a6fb4">LOW</span></td><td>suspected<br><small>MEDIUM</small></td><td><strong>GraphQL returns verbose error messages</strong><div class="desc">An invalid query produced detailed error messages (e.g. field suggestions or traces) that can aid schema discovery even when introspection is off.</div><div class="rec"><b>Remediation:</b> Return generic GraphQL errors in production; disable suggestions.</div><div class="ev"><b>Evidence:</b> <code>{"has_suggestions": true, "occurrences": 1}</code></div></td><td><code>GRAPHQL-ERROR-VERBOSE</code><br><small>API8:2023</small></td><td class="tgt"><code>https://api.lab.local/graphql</code></td></tr>
<tr data-sev="LOW"><td><span class="pill" style="background:#2a6fb4">LOW</span></td><td>informational<br><small>MEDIUM</small></td><td><strong>JWT payload carries sensitive claims</strong><div class="desc">The payload (which is base64-encoded, not encrypted) contains claim(s) ['role']. Anyone holding the token can read them.</div><div class="rec"><b>Remediation:</b> Minimise claims; keep PII/privilege data server-side or in an encrypted (JWE) token.</div><div class="ev"><b>Evidence:</b> <code>{"claims": ["role"], "occurrences": 1}</code></div></td><td><code>JWT-SENSITIVE-CLAIMS</code><br><small>API2:2023</small></td><td class="tgt"><code></code></td></tr>
<tr data-sev="LOW"><td><span class="pill" style="background:#2a6fb4">LOW</span></td><td>confirmed<br><small>MEDIUM</small></td><td><strong>Exposed Prometheus/metrics endpoint: /metrics</strong><div class="desc">/metrics returned HTTP 200 (application/json). This path is reachable and should be reviewed for whether it belongs on this surface.</div><div class="rec"><b>Remediation:</b> Restrict metrics/debug endpoints to internal networks.</div><div class="mv"><b>Manual verification:</b> Open the path and confirm it exposes sensitive data/functionality.</div><div class="ev"><b>Evidence:</b> <code>{"status_code": 200, "content_type": "application/json", "catch_all_baseline": false, "occurrences": 1}</code></div></td><td><code>EXPOSURE-TELEMETRY</code><br><small>API9:2023</small></td><td class="tgt"><code>https://api.lab.local/metrics</code></td></tr>
<tr data-sev="LOW"><td><span class="pill" style="background:#2a6fb4">LOW</span></td><td>informational<br><small>LOW</small></td><td><strong>Potentially sensitive route: GET /admin/users</strong><div class="desc">Route matched sensitive keyword(s) ['admin']. This is a prioritisation hint for manual review, not a vulnerability.</div><div class="mv"><b>Manual verification:</b> Review access control and exposure of this route manually.</div><div class="ev"><b>Evidence:</b> <code>{"keywords": ["admin"], "secured": true, "occurrences": 1}</code></div></td><td><code>INVENTORY-SENSITIVE-ROUTE</code><br><small>API9:2023</small></td><td class="tgt"><code>GET /admin/users</code></td></tr>
<tr data-sev="LOW"><td><span class="pill" style="background:#2a6fb4">LOW</span></td><td>inconclusive<br><small>LOW</small></td><td><strong>No throttling observed in a small bounded burst</strong><div class="desc">12 request(s) completed without any 429 or rate-limit header. A small burst cannot prove the absence of rate limiting; limits may be higher than the configured, deliberately low, request budget.</div><div class="rec"><b>Remediation:</b> Confirm rate limits exist for authentication, costly and write endpoints.</div><div class="mv"><b>Manual verification:</b> With explicit authorisation, test closer to the documented limit in a staging environment.</div><div class="ev"><b>Evidence:</b> <code>{"sent": 12, "avg_latency_ms": 0.1, "occurrences": 1}</code></div></td><td><code>RATE-NO-SIGNAL</code><br><small>API4:2023</small></td><td class="tgt"><code>https://api.lab.local/ping</code></td></tr>
<tr data-sev="LOW"><td><span class="pill" style="background:#2a6fb4">LOW</span></td><td>suspected<br><small>LOW</small></td><td><strong>Nested query accepted (no obvious depth limit)</strong><div class="desc">A bounded depth-5 query returned HTTP 200. The server accepted the nested query; a (deliberately bounded) probe cannot prove exploitability, but absence of a limit is worth manual review.</div><div class="mv"><b>Manual verification:</b> In a lab, measure complexity limits carefully; never stress shared infrastructure.</div><div class="ev"><b>Evidence:</b> <code>{"depth": 5, "status_code": 200, "rejected": false, "occurrences": 1}</code></div></td><td><code>GRAPHQL-DEPTH-LIMIT</code><br><small>API4:2023</small></td><td class="tgt"><code>https://api.lab.local/graphql</code></td></tr>
<tr data-sev="LOW"><td><span class="pill" style="background:#2a6fb4">LOW</span></td><td>suspected<br><small>LOW</small></td><td><strong>Possible Email address in response</strong><div class="desc">The response from https://api.lab.local/debug/config contains 1 match(es) for 'Email address'. Confirm whether this data should be returned to this caller and whether it is real (not seeded test data).</div><div class="rec"><b>Remediation:</b> Remove sensitive values from responses; return only authorised, minimal fields.</div><div class="mv"><b>Manual verification:</b> Inspect the raw response and confirm the value is a real secret/PII, not a fixture.</div><div class="ev"><b>Evidence:</b> <code>{"pattern": "Email address", "count": 1, "sample": "ops…al (len=13)", "occurrences": 1}</code></div></td><td><code>LEAK-EMAIL-ADDRESS</code><br><small>API3:2023</small></td><td class="tgt"><code>https://api.lab.local/debug/config</code></td></tr>
<tr data-sev="INFO"><td><span class="pill" style="background:#6b7280">INFO</span></td><td>informational<br><small>HIGH</small></td><td><strong>Target responded with HTTP 200</strong><div class="desc">https://api.lab.local returned status 200 (application/json).</div><div class="ev"><b>Evidence:</b> <code>{"status_code": 200, "content_type": "application/json", "elapsed_ms": 0.2, "occurrences": 1}</code></div></td><td><code>RECON-AVAILABILITY</code><br><small></small></td><td class="tgt"><code>https://api.lab.local</code></td></tr>
<tr data-sev="INFO"><td><span class="pill" style="background:#6b7280">INFO</span></td><td>informational<br><small>HIGH</small></td><td><strong>Specification describes 5 operation(s)</strong><div class="desc">API title: Demo Lab API, version: 1.2.0.</div><div class="ev"><b>Evidence:</b> <code>{"operation_count": 5, "version": "1.2.0", "occurrences": 1}</code></div></td><td><code>INVENTORY-SUMMARY</code><br><small>API9:2023</small></td><td class="tgt"><code></code></td></tr>
<tr data-sev="INFO"><td><span class="pill" style="background:#6b7280">INFO</span></td><td>informational<br><small>MEDIUM</small></td><td><strong>HTTP methods advertised by the server</strong><div class="desc">The server advertised the following methods via OPTIONS/Allow: GET, OPTIONS</div><div class="mv"><b>Manual verification:</b> Verify that write methods (PUT/DELETE/PATCH) are intended on this route.</div><div class="ev"><b>Evidence:</b> <code>{"methods": ["GET", "OPTIONS"], "occurrences": 1}</code></div></td><td><code>RECON-METHODS</code><br><small></small></td><td class="tgt"><code>https://api.lab.local</code></td></tr>
<tr data-sev="INFO"><td><span class="pill" style="background:#6b7280">INFO</span></td><td>informational<br><small>MEDIUM</small></td><td><strong>Browser header 'content-security-policy' absent (contextual, likely N/A)</strong><div class="desc">'content-security-policy' is missing. Primarily a browser control; relevant only if the API serves HTML/docs. This endpoint does not appear to serve HTML, so the header is typically not required for an API.</div><div class="ev"><b>Evidence:</b> <code>{"occurrences": 1}</code></div></td><td><code>CONFIG-HEADER-CONTEXTUAL</code><br><small>API8:2023</small></td><td class="tgt"><code>https://api.lab.local</code></td></tr>
<tr data-sev="INFO"><td><span class="pill" style="background:#6b7280">INFO</span></td><td>informational<br><small>MEDIUM</small></td><td><strong>Browser header 'x-frame-options' absent (contextual, likely N/A)</strong><div class="desc">'x-frame-options' is missing. Clickjacking control; relevant only for browser-rendered responses. This endpoint does not appear to serve HTML, so the header is typically not required for an API.</div><div class="ev"><b>Evidence:</b> <code>{"occurrences": 1}</code></div></td><td><code>CONFIG-HEADER-CONTEXTUAL</code><br><small>API8:2023</small></td><td class="tgt"><code>https://api.lab.local</code></td></tr></tbody></table>
<div class="meta"><h3>Run metadata</h3><table><tr><th>Base Url</th><td>https://api.lab.local</td></tr><tr><th>Dry Run</th><td>False</td></tr><tr><th>Requests Made</th><td>52</td></tr></table></div>
<footer>Generated by api-pentesting-toolkit. This report is produced by automated checks against an authorised target. Findings require human triage; see each finding's verification note. Severity is the estimated impact if confirmed; status distinguishes confirmed, suspected and inconclusive results.</footer>
<script>
const active=new Set();
document.querySelectorAll('.card').forEach(c=>c.addEventListener('click',()=>{
const s=c.dataset.sev; if(active.has(s)){active.delete(s);c.classList.add('off');}else{active.add(s);c.classList.remove('off');}
const any=active.size>0;
document.querySelectorAll('#tb tr').forEach(r=>{
r.style.display=(!any||active.has(r.dataset.sev))?'':'none';});
}));
</script>
</body></html>