← All finding types

trust_boundary_violation

CWE-501

Trust Boundary Violation — a PullGuard finding type. Findings of this type appear in the PR comment, Step Summary, SARIF (GitHub Security tab / IDE viewers), and the HTML report, each with severity, location, and the remediation guidance below.

How to fix

Validate request data before storing it in the session — or store a server-derived value low effort

// WRONG — any later code that reads the attribute trusts the client
session.setAttribute("role", request.getParameter("role"));

// RIGHT — store what the SERVER established, after validation
String role = roleService.roleFor(authenticatedUser);  // never the request
session.setAttribute("role", role);

// RIGHT — when a request value must be kept, validate it against an allowlist first
String lang = request.getParameter("lang");
if (SUPPORTED_LANGUAGES.contains(lang)) {
  session.setAttribute("lang", lang);
}

Triage

Suppress a confirmed non-issue with a committed .pullguardignore entry (pullguard ignore locally, or comment /pullguard ignore <fingerprint> <reason> on the PR — the fingerprint is printed in the PR comment’s Triage section). Entries support expiresAt for time-boxed snoozes.

Security findings at major or critical severity — and any critical finding — always surface: .pullguardignore cannot hide them. The reviewed paths that keep them visible are acknowledged (reviewed, stays in reports) and, for a confirmed false positive, a reasoned false_positive entry — visible and audited, excluded only from the merge block.