Detect server-side request forgery (SSRF) before merge.

See how server-side request forgery (SSRF) fits local review, which evidence Code Radar produces, where coverage ends, and how trusted findings move into CI.

Check this risk locally Review detection evidence

radar scan . --quick

What server-side request forgery (SSRF) means here.

The server-side request forgery (SSRF) rule identifies review patterns that can create exploitable behavior or hide material maintenance risk, then returns the affected location, severity, confidence, and remediation context.

Rule reference

Evidence to inspect

Use “Detect server-side request forgery (SSRF) before merge.” as the scope for this decision: verify the input, finding detail, workflow handoff, and product boundary before you install or buy.

CriterionEvidence to inspectBoundary

Input scopeSelected files, configuration, scan mode, and enabled rules.Only included paths and configured checks are evaluated.

Finding detailFile, line, rule ID, severity, explanation, and repair direction.Illustrative output is not a result from your repository.

Workflow handoffLocal result, report format, agent context, and optional CI signal.Enable exports or CI only when the workflow needs them.

Decision fitUse the same criteria on a real repository before choosing a plan or tool.No universal winner or guaranteed outcome is claimed.

Rule reference

Check this risk locally

Coverage and concrete signals

Detect untrusted URLs reaching outbound requests without an allowlist.

Audience: Developers and reviewers deciding how to handle server-side request forgery (SSRF) findings before merge.
Evidence to inspect before you trust the result.: Identify the user-controlled URL, the outbound client, and the allowlist or service selector used by the safer example.
Boundary: Internal service URLs or fixed destinations may be safe when the allowlist is enforced; test redirects, DNS rebinding, and unexpected schemes before closing the finding.
Rule ID: RADAR-SEC-SSRF

Risky pattern / Safer pattern

server-side request forgery (SSRF): A useful result must be explainable to a developer and portable to the next review surface. Inspect the concrete evidence below before changing team policy.

Risky patternSafer pattern

fetch(request.query.url);fetch(allowlistedServiceUrl(request.query.service));

From local signal to shared gate.

server-side request forgery (SSRF): Use the smallest workflow that proves value. Each later step should reuse evidence the team already understands. Identify the user-controlled URL, the outbound client, and the allowlist or service selector used by the safer example.

StepCommand or actionDecision

1Run a quick local scanIs the signal useful?

2Inspect and repair findingsIs the fix specific and reproducible?

3Export portable evidenceDoes the reviewer need SARIF, JSON, or HTML?

4Promote the trusted threshold to CIWhich severity should block a pull request?

radar scan . --quick
radar scan . --format sarif --fail-on high

Official source

Primary sources

Validate the workflow on your own code.

Apply this page’s evidence to one real repository. For “Detect server-side request forgery (SSRF) before merge.”, confirm which finding is produced, whether the proposed next step is reproducible, and where local scanning, reports, agents, or CI should stop or expand.