# Security Audit Report — adapto-cms-cli - **Report ID:** `a8cefd30-2e08-4432-b133-1c223ae1171a` - **Generated:** 2026-08-11T15:54:27.206322+00:00 - **Signature:** unsigned (cosign keyless signing runs in CI; Req 22.4) ## 1. Executive Summary **Badge:** Unsafe (composite) **Security score:** 77.8 | Scanner | Badge | | --- | --- | | agent-audit-kit | Verified | | agentshield | not_applicable | | bearer | Unsafe | | capslock | unavailable | | cisco-skill-scanner | Verified | | govulncheck | unavailable | | nerlo-behavioral | Verified | | nerlo-install-instruction | Unsafe | | osv-scanner | Verified | | trivy | Caution | | trivy_image | not_applicable | | Severity | Findings | | --- | --- | | critical | 0 | | high | 158 | | medium | 1 | | low | 2 | | informational | 29 | adapto-cms-cli is NOT recommended for integration: the scan surfaced 0 critical and 158 high-severity findings. Treat the Per-Scanner Detail section as a remediation worklist and re-scan before reconsidering. ## 2. Source Provenance - **Repository:** https://github.com/adaptocms/adapto-cms-cli - **Commit scanned:** `unknown` - **License:** unknown - **Maintainer:** unknown - **Version:** unknown ## 3. Per-Scanner Detail ### agentshield (v1.4.0) — not_applicable / n/a No findings. ### cisco-skill-scanner (v2.0.11) — Verified / 94.0 - **[low] Dangerous data flow in command pipeline** — Pipeline downloads data from the network and executes it: 'curl -sSL https://raw.githubusercontent.com/adaptocms/adapto-cms-cli/main/scripts/install.sh \| bash'. This is a remote code execution pattern. (Note: found in documentation file - may be instructional rather than executable.) (/repo/README.md:1) - **[informational] Vague skill description** — [mcp_server policy: capability-matches-purpose class; severity low -> informational] Skill description is too short (16 chars). Provide detailed explanation. (/repo/SKILL.md:None) - **[informational] Skill does not specify a license** — Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms. (/repo/SKILL.md:None) - **[low] Dangerous data flow in command pipeline** — Pipeline downloads data from the network and executes it: 'curl -sSL https://raw.githubusercontent.com/adaptocms/adapto-cms-cli/main/scripts/install.sh \| bash'. This is a remote code execution pattern. (Note: appears to be instructional install text in SKILL.md; review URL trust and pinning.) (/repo/SKILL.md:1) - **[informational] Vague skill description** — [mcp_server policy: capability-matches-purpose class; severity low -> informational] Skill description is too short (16 chars). Provide detailed explanation. (/repo/cmd/llminfo/SKILL.md:None) - **[informational] Skill does not specify a license** — Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms. (/repo/cmd/llminfo/SKILL.md:None) ### agent-audit-kit (v0.3.26) — Verified / 95.0 - **[medium] Third-party GitHub Action not pinned by full commit SHA** — A workflow in '.github/workflows/' uses a third-party Action ('owner/action@ref') where 'ref' is a tag or branch name instead of a 40-character commit SHA. A repo-takeover of the Action's publisher can re-point the tag to a malicious revision — the downstream repo consuming it will happily run the new code with 'GITHUB_TOKEN' and write permissions. GitHub's April 2026 Security Roadmap ships Immutable Actions and makes SHA pinning the default policy. (.github/workflows/release.yml:44) ### bearer (v2.0.2) — Unsafe / 0.0 - **[high] Permissive file assignment** — \#\# Description Setting overly permissive file permissions exposes your system to risks such as unauthorized access, data tampering, and potential system compromise. This vulnerability arises when files are created or updated without adequately restrictive permissions, allowing unauthorized users to read, modify, or execute files. \#\# Remediations - **Do not** use overly permissive file permissions, such as '0777', which grants read, write, and execute permissions to all users. - **Do** set fil (/repo/tools/gendocs/main.go:45) - **[high] Unsanitized user input in file path** — \#\# Description Using user input to dynamically construct file paths without proper sanitization introduces a high security risk. This practice can allow attackers to manipulate file paths to access or alter sensitive files, potentially leading to data breaches or system compromise. It is essential to sanitize user input before using it in file system operations to prevent path traversal attacks. \#\# Remediations - **Do not** use unsanitized user input directly in file path construction. This c (/repo/cmd/files/files.go:551) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:5800) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:5838) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:5874) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:5908) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:5953) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6014) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6052) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6092) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6143) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6181) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6221) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6250) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6288) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6328) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6368) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6408) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6455) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6493) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6540) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6585) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6619) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6653) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6691) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6720) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6754) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6799) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6846) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6893) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6940) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:6976) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:7003) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:7054) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:7130) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:7186) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:7244) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:7280) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:7314) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:7359) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:7406) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:7435) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:7462) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:7639) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:7692) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:7743) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:7935) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:7984) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:8033) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:8093) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:8144) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:8193) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:8242) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:8291) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:8351) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:8513) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:8566) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:8617) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:8666) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:8715) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:8775) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:8826) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:8882) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:8938) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:8987) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:9036) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:9096) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:9258) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:9311) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:9362) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:9411) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:9460) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:9520) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:9705) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:9765) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:9827) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:9889) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:9947) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:10130) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:10186) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:10242) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:10309) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:10367) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:10423) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:10479) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:10546) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:10724) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:10766) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:10821) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:10872) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:10921) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:10981) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:11032) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:11088) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:11155) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:11220) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:11271) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:11353) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:11406) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:11479) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:11559) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:11608) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:11657) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:11706) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:11755) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:11815) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:11877) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12055) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12108) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12159) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12335) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12384) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12433) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12493) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12544) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12593) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12642) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12702) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12746) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12773) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12800) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12838) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12878) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12925) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12959) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:12993) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13038) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13074) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13119) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13162) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13196) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13241) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13284) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13311) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13360) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13413) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13543) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13592) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13641) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13690) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13793) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13846) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13897) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:13957) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:14026) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:14075) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:14148) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:14184) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:14218) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:14252) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:14297) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:14326) - **[high] Unsanitized user input in HTTP request (SSRF)** — \#\# Description Including unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems. \#\# Remediations - **Do no (/repo/internal/client/generated.go:14360) - **[high] Unsanitized user input in file path** — \#\# Description Unsanitized user input in file path resolution can lead to security vulnerabilities. This issue arises when an application directly uses input from the user to determine file paths or names without proper validation or sanitization. Attackers can exploit this to access unauthorized files or directories, leading to data breaches or other security compromises. \#\# Remediations - **Do not** directly use user input in file paths without sanitization. This prevents attackers from man (/repo/scripts/downgrade_openapi.py:34) - **[high] Unsanitized user input in file path** — \#\# Description Unsanitized user input in file path resolution can lead to security vulnerabilities. This issue arises when an application directly uses input from the user to determine file paths or names without proper validation or sanitization. Attackers can exploit this to access unauthorized files or directories, leading to data breaches or other security compromises. \#\# Remediations - **Do not** directly use user input in file paths without sanitization. This prevents attackers from man (/repo/scripts/downgrade_openapi.py:37) ### nerlo-behavioral (v0.1.0) — Verified / 100.0 No findings. ### nerlo-install-instruction (v0.1.0) — Unsafe / 59.0 - **[high] opt.nerlo-rules.nerlo-install-pipe-to-shell** — Documentation instructs piping a downloaded artifact directly into a shell (curl/wget/iwr ... \| bash/sh/iex). This is the curl-pipe-bash install shape used by the ClawHub skill droppers and countless malware loaders — the fetched payload is executed with zero inspection. Confirm this is expected; it is a strong weaponized-documentation signal. (/repo/README.md:10) - **[high] opt.nerlo-rules.nerlo-install-fetch-raw-then-run** — Documentation directs fetching a raw file (raw.githubusercontent.com, a gist raw URL, or a GitHub release asset) and executing it. Fetch-then-run of an untrusted raw artifact is a fetch-and-execute install directive — the FakeGit "download and run" shape. Confirm the artifact and origin. (/repo/README.md:10) ### capslock (vv0.3.2) — unavailable / n/a No findings. ### trivy (v0.71.0) — Caution / 84.0 - **[informational] Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows** — NewNTUnicodeString does not check for string length overflow. When provided with a string that overflows the maximum size of a NTUnicodeString (a 16-bit number of bytes), it returns a truncated string rather than an error. (go.mod:None) - **[high] golang.org/x/text: golang.org/x/text: Denial of Service via invalid UTF-8 input** — A norm.Iter can enter an infinite loop when handling input containing invalid UTF-8 bytes. (go.mod:None) ### osv-scanner (v2.3.8) — Verified / 88.0 - **[informational] GO-2026-5024 — Go golang.org/x/sys@0.39.0** — aliases: CVE-2026-39824, GO-2026-5024 (/repo/go.mod:None) - **[informational] GO-2026-5970 — Go golang.org/x/text@0.32.0** — aliases: CVE-2026-56852, GO-2026-5970 (/repo/go.mod:None) - **[informational] GO-2026-4601 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-25679, CVE-2026-25679, GO-2026-4601 (/repo/go.mod:None) - **[informational] GO-2026-4602 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-27139, CVE-2026-27139, GO-2026-4602 (/repo/go.mod:None) - **[informational] GO-2026-4603 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-27142, CVE-2026-27142, GO-2026-4603 (/repo/go.mod:None) - **[informational] GO-2026-4864 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-32282, CVE-2026-32282, GO-2026-4864 (/repo/go.mod:None) - **[informational] GO-2026-4865 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-32289, CVE-2026-32289, GO-2026-4865 (/repo/go.mod:None) - **[informational] GO-2026-4869 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-32288, CVE-2026-32288, GO-2026-4869 (/repo/go.mod:None) - **[informational] GO-2026-4870 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-32283, CVE-2026-32283, GO-2026-4870 (/repo/go.mod:None) - **[informational] GO-2026-4918 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-33814, CVE-2026-33814, GO-2026-4918 (/repo/go.mod:None) - **[informational] GO-2026-4946 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-32281, CVE-2026-32281, GO-2026-4946 (/repo/go.mod:None) - **[informational] GO-2026-4947 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-32280, CVE-2026-32280, GO-2026-4947 (/repo/go.mod:None) - **[informational] GO-2026-4970 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-39822, CVE-2026-39822, GO-2026-4970 (/repo/go.mod:None) - **[informational] GO-2026-4971 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-39836, CVE-2026-39836, GO-2026-4971 (/repo/go.mod:None) - **[informational] GO-2026-4976 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-39825, CVE-2026-39825, GO-2026-4976 (/repo/go.mod:None) - **[informational] GO-2026-4977 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-42499, CVE-2026-42499, GO-2026-4977 (/repo/go.mod:None) - **[informational] GO-2026-4980 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-39826, CVE-2026-39826, GO-2026-4980 (/repo/go.mod:None) - **[informational] GO-2026-4981 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-33811, CVE-2026-33811, GO-2026-4981 (/repo/go.mod:None) - **[informational] GO-2026-4982 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-39823, CVE-2026-39823, GO-2026-4982 (/repo/go.mod:None) - **[informational] GO-2026-4986 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-39820, CVE-2026-39820, GO-2026-4986 (/repo/go.mod:None) - **[informational] GO-2026-5037 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-27145, CVE-2026-27145, GO-2026-5037 (/repo/go.mod:None) - **[informational] GO-2026-5038 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-42504, CVE-2026-42504, GO-2026-5038 (/repo/go.mod:None) - **[informational] GO-2026-5039 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-42507, CVE-2026-42507, GO-2026-5039 (/repo/go.mod:None) - **[informational] GO-2026-5856 — Go stdlib@1.25.7** — aliases: BIT-golang-2026-42505, CVE-2026-42505, GO-2026-5856 (/repo/go.mod:None) ### trivy_image (v0.71.0) — not_applicable / n/a No findings. ### govulncheck (vv1.6.0) — unavailable / n/a No findings. ## 4. Threat Model Threat model synthesis has not yet run for this scan. This section is generated by the registry's LLM pipeline (Req 22.3) and will appear in the next regeneration of this report. ## 5. Audit Chain - **Scan job:** `439d0109-14a8-4e9f-9b6b-f4c7043c792d` - **Completed:** 2026-08-11T09:39:07.777380+00:00 - **Scanner base image:** `us-central1-docker.pkg.dev/nerlo-vsk-prod/nerlo/scanner-base@sha256:9d1af4718dec7905ca5161a77f180bca93d3ae4e419c98e200887067314335c4` - **AI decision log entries:** 2 - `84a04142-638f-44e7-b3bf-3bbbd2ef91cc` - `fe2d516b-3589-441d-b74d-9701c6d8f4e4` ## 6. Appendix — Raw Scanner Output ```json [ { "scanner_name": "agentshield", "scanner_version": "1.4.0", "score": 100.0, "scanner_badge": "Verified", "findings": [], "execution_duration_seconds": 0.16218955803196877, "status": "not_applicable", "examined": { "unit": "scan_targets", "count": 0 }, "metadata": { "source": "npm", "source_url": "https://www.npmjs.com/package/ecc-agentshield", "install_command": "npm install -g ecc-agentshield@1.4.0", "scans_performed": [] }, "display_score": null, "display_badge": "not_applicable" }, { "scanner_name": "cisco-skill-scanner", "scanner_version": "2.0.11", "score": 94.0, "scanner_badge": "Verified", "findings": [ { "tool_name": "cisco-skill-scanner", "severity": "low", "category": "command_injection", "file_path": "/repo/README.md", "line_number": 1, "rule_identifier": "PIPELINE_TAINT_FLOW", "title": "Dangerous data flow in command pipeline", "description": "Pipeline downloads data from the network and executes it: `curl -sSL https://raw.githubusercontent.com/adaptocms/adapto-cms-cli/main/scripts/install.sh | bash`. This is a remote code execution pattern. (Note: found in documentation file - may be instructional rather than executable.)", "remediation": "Review the command pipeline. Avoid piping sensitive data to network commands or shell execution." }, { "tool_name": "cisco-skill-scanner", "severity": "informational", "category": "social_engineering", "file_path": "/repo/SKILL.md", "line_number": null, "rule_identifier": "SOCIAL_ENG_VAGUE_DESCRIPTION", "title": "Vague skill description", "description": "[mcp_server policy: capability-matches-purpose class; severity low -> informational] Skill description is too short (16 chars). Provide detailed explanation.", "remediation": "Provide a clear, detailed description of what the skill does and when to use it" }, { "tool_name": "cisco-skill-scanner", "severity": "informational", "category": "policy_violation", "file_path": "/repo/SKILL.md", "line_number": null, "rule_identifier": "MANIFEST_MISSING_LICENSE", "title": "Skill does not specify a license", "description": "Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms.", "remediation": "Add 'license' field to SKILL.md frontmatter (e.g., MIT, Apache-2.0)" }, { "tool_name": "cisco-skill-scanner", "severity": "low", "category": "command_injection", "file_path": "/repo/SKILL.md", "line_number": 1, "rule_identifier": "PIPELINE_TAINT_FLOW", "title": "Dangerous data flow in command pipeline", "description": "Pipeline downloads data from the network and executes it: `curl -sSL https://raw.githubusercontent.com/adaptocms/adapto-cms-cli/main/scripts/install.sh | bash`. This is a remote code execution pattern. (Note: appears to be instructional install text in SKILL.md; review URL trust and pinning.)", "remediation": "Review the command pipeline. Avoid piping sensitive data to network commands or shell execution." }, { "tool_name": "cisco-skill-scanner", "severity": "informational", "category": "social_engineering", "file_path": "/repo/cmd/llminfo/SKILL.md", "line_number": null, "rule_identifier": "SOCIAL_ENG_VAGUE_DESCRIPTION", "title": "Vague skill description", "description": "[mcp_server policy: capability-matches-purpose class; severity low -> informational] Skill description is too short (16 chars). Provide detailed explanation.", "remediation": "Provide a clear, detailed description of what the skill does and when to use it" }, { "tool_name": "cisco-skill-scanner", "severity": "informational", "category": "policy_violation", "file_path": "/repo/cmd/llminfo/SKILL.md", "line_number": null, "rule_identifier": "MANIFEST_MISSING_LICENSE", "title": "Skill does not specify a license", "description": "Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms.", "remediation": "Add 'license' field to SKILL.md frontmatter (e.g., MIT, Apache-2.0)" } ], "execution_duration_seconds": 7.190255146007985, "status": "complete", "examined": { "unit": "skills", "count": 2 }, "metadata": { "source": "pypi", "source_url": "https://pypi.org/project/cisco-ai-skill-scanner/2.0.11/", "report_type": "cisco-skill-sast", "analyzers_used": [ "bytecode", "pipeline", "static_analyzer" ], "skills_scanned": [ "repo", "llminfo" ], "install_command": "pip install --require-hashes -r docker/scanner-base/cisco-skill-scanner/requirements.txt", "severity_counts": { "low": 2, "high": 0, "medium": 0, "critical": 0, "informational": 4 }, "artifact_type_policy": "mcp_server", "downweighted_findings": 2 }, "display_score": 94.0, "display_badge": "Verified" }, { "scanner_name": "agent-audit-kit", "scanner_version": "0.3.26", "score": 95.0, "scanner_badge": "Verified", "findings": [ { "tool_name": "agent-audit-kit", "severity": "medium", "category": "supply-chain", "file_path": ".github/workflows/release.yml", "line_number": 44, "rule_identifier": "AAK-GHA-IMMUTABLE-001", "title": "Third-party GitHub Action not pinned by full commit SHA", "description": "A workflow in `.github/workflows/` uses a third-party Action (`owner/action@ref`) where `ref` is a tag or branch name instead of a 40-character commit SHA. A repo-takeover of the Action's publisher can re-point the tag to a malicious revision \u2014 the downstream repo consuming it will happily run the new code with `GITHUB_TOKEN` and write permissions. GitHub's April 2026 Security Roadmap ships Immutable Actions and makes SHA pinning the default policy.", "remediation": "Repin third-party Actions to a 40-character commit SHA and add a `# v1.2.3`-style trailing comment for humans. First-party Actions under `actions/` and `github/` are exempt (they now ship Immutable Actions). Dependabot will auto-bump SHA pins when `update-type: all` is set." } ], "execution_duration_seconds": 3.6755275020259432, "status": "complete", "examined": { "unit": "files", "count": 48 }, "metadata": { "source": "pypi", "source_url": "https://pypi.org/project/agent-audit-kit/0.3.26/", "report_type": "agent-audit-kit-sast", "install_command": "pip install --require-hashes -r docker/scanner-base/agent-audit-kit/requirements.txt", "rules_evaluated": 211, "severity_counts": { "low": 0, "high": 0, "medium": 1, "critical": 0, "informational": 0 } }, "display_score": 95.0, "display_badge": "Verified" }, { "scanner_name": "bearer", "scanner_version": "2.0.2", "score": 0.0, "scanner_badge": "Unsafe", "findings": [ { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/tools/gendocs/main.go", "line_number": 45, "rule_identifier": null, "title": "Permissive file assignment", "description": "## Description\n\nSetting overly permissive file permissions exposes your system to risks such as unauthorized access, data tampering, and potential system compromise. This vulnerability arises when files are created or updated without adequately restrictive permissions, allowing unauthorized users to read, modify, or execute files.\n\n## Remediations\n\n- **Do not** use overly permissive file permissions, such as `0777`, which grants read, write, and execute permissions to all users.\n- **Do** set fil", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/cmd/files/files.go", "line_number": 551, "rule_identifier": null, "title": "Unsanitized user input in file path", "description": "## Description\n\nUsing user input to dynamically construct file paths without proper sanitization introduces a high security risk. This practice can allow attackers to manipulate file paths to access or alter sensitive files, potentially leading to data breaches or system compromise. It is essential to sanitize user input before using it in file system operations to prevent path traversal attacks.\n\n## Remediations\n\n- **Do not** use unsanitized user input directly in file path construction. This c", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 5800, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 5838, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 5874, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 5908, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 5953, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6014, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6052, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6092, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6143, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6181, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6221, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6250, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6288, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6328, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6368, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6408, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6455, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6493, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6540, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6585, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6619, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6653, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6691, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6720, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6754, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6799, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6846, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6893, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6940, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 6976, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 7003, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 7054, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 7130, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 7186, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 7244, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 7280, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 7314, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 7359, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 7406, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 7435, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 7462, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 7639, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 7692, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 7743, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 7935, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 7984, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 8033, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 8093, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 8144, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 8193, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 8242, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 8291, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 8351, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 8513, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 8566, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 8617, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 8666, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 8715, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 8775, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 8826, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 8882, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 8938, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 8987, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 9036, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 9096, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 9258, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 9311, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 9362, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 9411, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 9460, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 9520, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 9705, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 9765, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 9827, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 9889, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 9947, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 10130, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 10186, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 10242, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 10309, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 10367, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 10423, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 10479, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 10546, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 10724, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 10766, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 10821, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 10872, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 10921, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 10981, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 11032, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 11088, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 11155, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 11220, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 11271, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 11353, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 11406, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 11479, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 11559, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 11608, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 11657, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 11706, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 11755, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 11815, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 11877, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12055, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12108, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12159, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12335, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12384, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12433, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12493, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12544, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12593, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12642, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12702, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12746, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12773, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12800, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12838, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12878, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12925, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12959, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 12993, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13038, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13074, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13119, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13162, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13196, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13241, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13284, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13311, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13360, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13413, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13543, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13592, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13641, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13690, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13793, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13846, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13897, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 13957, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 14026, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 14075, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 14148, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 14184, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 14218, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 14252, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 14297, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 14326, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/internal/client/generated.go", "line_number": 14360, "rule_identifier": null, "title": "Unsanitized user input in HTTP request (SSRF)", "description": "## Description\n\nIncluding unsanitized user input in HTTP requests puts your application at risk of Server-Side Request Forgery (SSRF). This is a security vulnerability that occurs when a server-side application makes HTTP requests to arbitrary URLs controlled by the user. SSRF can be exploited by attackers to target internal systems behind firewalls that are otherwise inaccessible from the external network, by tricking the server into making requests to these systems.\n\n## Remediations\n\n- **Do no", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/scripts/downgrade_openapi.py", "line_number": 34, "rule_identifier": null, "title": "Unsanitized user input in file path", "description": "## Description\n\nUnsanitized user input in file path resolution can lead to security vulnerabilities. This issue arises when an application directly uses input from the user to determine file paths or names without proper validation or sanitization. Attackers can exploit this to access unauthorized files or directories, leading to data breaches or other security compromises.\n\n## Remediations\n\n- **Do not** directly use user input in file paths without sanitization. This prevents attackers from man", "remediation": null }, { "tool_name": "bearer", "severity": "high", "category": null, "file_path": "/repo/scripts/downgrade_openapi.py", "line_number": 37, "rule_identifier": null, "title": "Unsanitized user input in file path", "description": "## Description\n\nUnsanitized user input in file path resolution can lead to security vulnerabilities. This issue arises when an application directly uses input from the user to determine file paths or names without proper validation or sanitization. Attackers can exploit this to access unauthorized files or directories, leading to data breaches or other security compromises.\n\n## Remediations\n\n- **Do not** directly use user input in file paths without sanitization. This prevents attackers from man", "remediation": null } ], "execution_duration_seconds": 36.17440923501272, "status": "complete", "examined": { "unit": "files", "count": 38 }, "metadata": { "source": "github-releases", "source_url": "https://github.com/Bearer/bearer", "report_type": "security", "rules_loaded": 554, "install_command": "curl -sfL https://raw.githubusercontent.com/Bearer/bearer/main/contrib/install.sh | sh -s -- -b /usr/local/bin \"v2.0.2\"", "severity_counts": { "low": 0, "high": 155, "medium": 0, "critical": 0, "informational": 0 } }, "display_score": 0.0, "display_badge": "Unsafe" }, { "scanner_name": "nerlo-behavioral", "scanner_version": "0.1.0", "score": 100.0, "scanner_badge": "Verified", "findings": [], "execution_duration_seconds": 13.238877695985138, "status": "complete", "examined": { "unit": "files", "count": 29 }, "metadata": { "source": "nerlo-original", "source_url": "https://github.com/nerlo-ai/nerlo", "report_type": "nerlo-behavioral", "ruleset_path": "/opt/nerlo-rules/exfiltration.yaml", "ruleset_paths": [ "/opt/nerlo-rules/exfiltration.yaml", "/opt/nerlo-rules/clipboard_exfiltration.yaml", "/opt/nerlo-rules/rce_endpoint.yaml", "/opt/nerlo-rules/taint_egress.yaml" ], "install_command": "pip install 'semgrep==1.97.0'", "merged_invocation": true }, "display_score": 100.0, "display_badge": "Verified" }, { "scanner_name": "nerlo-install-instruction", "scanner_version": "0.1.0", "score": 59.0, "scanner_badge": "Unsafe", "findings": [ { "tool_name": "nerlo-install-instruction", "severity": "high", "category": "install-instruction-exec", "file_path": "/repo/README.md", "line_number": 10, "rule_identifier": "opt.nerlo-rules.nerlo-install-pipe-to-shell", "title": "opt.nerlo-rules.nerlo-install-pipe-to-shell", "description": "Documentation instructs piping a downloaded artifact directly into a shell (curl/wget/iwr ... | bash/sh/iex). This is the curl-pipe-bash install shape used by the ClawHub skill droppers and countless malware loaders \u2014 the fetched payload is executed with zero inspection. Confirm this is expected; it is a strong weaponized-documentation signal.", "remediation": null }, { "tool_name": "nerlo-install-instruction", "severity": "high", "category": "install-instruction-exec", "file_path": "/repo/README.md", "line_number": 10, "rule_identifier": "opt.nerlo-rules.nerlo-install-fetch-raw-then-run", "title": "opt.nerlo-rules.nerlo-install-fetch-raw-then-run", "description": "Documentation directs fetching a raw file (raw.githubusercontent.com, a gist raw URL, or a GitHub release asset) and executing it. Fetch-then-run of an untrusted raw artifact is a fetch-and-execute install directive \u2014 the FakeGit \"download and run\" shape. Confirm the artifact and origin.", "remediation": null } ], "execution_duration_seconds": 13.240829564048909, "status": "complete", "examined": { "unit": "files", "count": 5 }, "metadata": { "source": "nerlo-original", "source_url": "https://github.com/nerlo-ai/nerlo", "report_type": "nerlo-install-instruction", "ruleset_path": "/opt/nerlo-rules/install_instructions.yaml", "ruleset_paths": [ "/opt/nerlo-rules/install_instructions.yaml", "/opt/nerlo-rules/cursor_rules.yaml" ], "install_command": "pip install 'semgrep==1.97.0'", "severity_counts": { "low": 0, "high": 2, "medium": 0, "critical": 0, "informational": 0 }, "merged_invocation": true }, "display_score": 59.0, "display_badge": "Unsafe" }, { "scanner_name": "capslock", "scanner_version": "v0.3.2", "score": 100.0, "scanner_badge": "Verified", "findings": [], "execution_duration_seconds": 2.7265439489856362, "status": "incomplete", "examined": null, "metadata": { "source": "go-module-proxy", "source_url": "https://github.com/google/capslock/releases/tag/v0.3.2", "report_type": "go-capability", "stderr_tail": "aptocms/adapto-cms-cli/internal/credentials)\n/repo/internal/config/config.go:5:2: could not import github.com/spf13/viper (no metadata for github.com/spf13/viper)\n/repo/internal/config/config.go:24:13: undefined: viper\n/repo/internal/config/config.go:25:13: undefined: viper\n/repo/internal/config/config.go:26:13: undefined: viper\n/repo/internal/config/config.go:27:13: undefined: viper\n/repo/internal/c(...truncated)\n(420 more errors)\n2026/08/11 09:38:31 Some packages had errors. Aborting analysis.", "vendor_mode": false, "error_message": "capslock produced no output over 37 .go file(s) \u2014 capslock writes nothing to stdout and exits 2 when it cannot load the requested packages, so this run carries no verdict", "install_command": "GOTOOLCHAIN=local GOFLAGS=-mod=mod GOSUMDB=sum.golang.org GOBIN=/usr/local/bin go install github.com/google/capslock/cmd/capslock@v0.3.2 # github.com/google/capslock v0.3.2 h1:0ZQa9YR8s9ewFu1g5w6Rgd/lW/4dga7qJew3K6Ql7aM=", "go_files_present": 37, "artifact_type_policy": "mcp_server", "expected_capabilities": [ "CAPABILITY_FILES", "CAPABILITY_NETWORK", "CAPABILITY_READ_SYSTEM_STATE", "CAPABILITY_REFLECT", "CAPABILITY_RUNTIME" ], "artifact_type_explicit": true }, "display_score": null, "display_badge": "unavailable" }, { "scanner_name": "trivy", "scanner_version": "0.71.0", "score": 84.0, "scanner_badge": "Caution", "findings": [ { "tool_name": "trivy", "severity": "informational", "category": "gomod", "file_path": "go.mod", "line_number": null, "rule_identifier": "CVE-2026-39824", "title": "Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows", "description": "NewNTUnicodeString does not check for string length overflow. When provided with a string that overflows the maximum size of a NTUnicodeString (a 16-bit number of bytes), it returns a truncated string rather than an error.", "remediation": "Upgrade golang.org/x/sys from v0.39.0 to 0.44.0 or later" }, { "tool_name": "trivy", "severity": "high", "category": "gomod", "file_path": "go.mod", "line_number": null, "rule_identifier": "CVE-2026-56852", "title": "golang.org/x/text: golang.org/x/text: Denial of Service via invalid UTF-8 input", "description": "A norm.Iter can enter an infinite loop when handling input containing invalid UTF-8 bytes.", "remediation": "Upgrade golang.org/x/text from v0.32.0 to 0.39.0 or later" } ], "execution_duration_seconds": 0.3531265609781258, "status": "complete", "examined": { "unit": "manifests", "count": 1 }, "metadata": { "source": "github-releases", "source_url": "https://github.com/aquasecurity/trivy/releases/tag/v0.71.0", "report_type": "filesystem-vulnerability", "install_command": "curl -sfL -o /tmp/trivy.deb https://github.com/aquasecurity/trivy/releases/download/v0.71.0/trivy_0.71.0_Linux-64bit.deb && echo ' /tmp/trivy.deb' | sha256sum -c - && dpkg -i /tmp/trivy.deb", "severity_counts": { "low": 0, "high": 1, "medium": 0, "critical": 0, "informational": 1 }, "manifests_scanned": [ "go.mod" ] }, "display_score": 84.0, "display_badge": "Caution" }, { "scanner_name": "osv-scanner", "scanner_version": "2.3.8", "score": 88.0, "scanner_badge": "Verified", "findings": [ { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-5024", "title": "GO-2026-5024 \u2014 Go golang.org/x/sys@0.39.0", "description": "aliases: CVE-2026-39824, GO-2026-5024", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-5970", "title": "GO-2026-5970 \u2014 Go golang.org/x/text@0.32.0", "description": "aliases: CVE-2026-56852, GO-2026-5970", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4601", "title": "GO-2026-4601 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-25679, CVE-2026-25679, GO-2026-4601", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4602", "title": "GO-2026-4602 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-27139, CVE-2026-27139, GO-2026-4602", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4603", "title": "GO-2026-4603 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-27142, CVE-2026-27142, GO-2026-4603", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4864", "title": "GO-2026-4864 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-32282, CVE-2026-32282, GO-2026-4864", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4865", "title": "GO-2026-4865 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-32289, CVE-2026-32289, GO-2026-4865", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4869", "title": "GO-2026-4869 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-32288, CVE-2026-32288, GO-2026-4869", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4870", "title": "GO-2026-4870 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-32283, CVE-2026-32283, GO-2026-4870", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4918", "title": "GO-2026-4918 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-33814, CVE-2026-33814, GO-2026-4918", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4946", "title": "GO-2026-4946 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-32281, CVE-2026-32281, GO-2026-4946", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4947", "title": "GO-2026-4947 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-32280, CVE-2026-32280, GO-2026-4947", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4970", "title": "GO-2026-4970 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-39822, CVE-2026-39822, GO-2026-4970", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4971", "title": "GO-2026-4971 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-39836, CVE-2026-39836, GO-2026-4971", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4976", "title": "GO-2026-4976 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-39825, CVE-2026-39825, GO-2026-4976", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4977", "title": "GO-2026-4977 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-42499, CVE-2026-42499, GO-2026-4977", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4980", "title": "GO-2026-4980 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-39826, CVE-2026-39826, GO-2026-4980", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4981", "title": "GO-2026-4981 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-33811, CVE-2026-33811, GO-2026-4981", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4982", "title": "GO-2026-4982 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-39823, CVE-2026-39823, GO-2026-4982", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-4986", "title": "GO-2026-4986 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-39820, CVE-2026-39820, GO-2026-4986", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-5037", "title": "GO-2026-5037 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-27145, CVE-2026-27145, GO-2026-5037", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-5038", "title": "GO-2026-5038 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-42504, CVE-2026-42504, GO-2026-5038", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-5039", "title": "GO-2026-5039 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-42507, CVE-2026-42507, GO-2026-5039", "remediation": null }, { "tool_name": "osv-scanner", "severity": "informational", "category": "Go", "file_path": "/repo/go.mod", "line_number": null, "rule_identifier": "GO-2026-5856", "title": "GO-2026-5856 \u2014 Go stdlib@1.25.7", "description": "aliases: BIT-golang-2026-42505, CVE-2026-42505, GO-2026-5856", "remediation": null } ], "execution_duration_seconds": 0.7554606809862889, "status": "complete", "examined": { "unit": "manifests", "count": 1 }, "metadata": { "source": "github-releases", "source_url": "https://github.com/google/osv-scanner/releases/tag/v2.3.8", "report_type": "osv-vulnerability", "ecosystems_seen": [ "Go" ], "install_command": "curl -sfL -o /usr/local/bin/osv-scanner https://github.com/google/osv-scanner/releases/download/v2.3.8/osv-scanner_linux_amd64 && echo ' /usr/local/bin/osv-scanner' | sha256sum -c - && chmod +x /usr/local/bin/osv-scanner", "severity_counts": { "low": 0, "high": 0, "medium": 0, "critical": 0, "informational": 24 }, "manifests_scanned": [ "/repo/go.mod" ], "finding_id_aliases": { "GO-2026-4601": [ "BIT-golang-2026-25679", "CVE-2026-25679" ], "GO-2026-4602": [ "BIT-golang-2026-27139", "CVE-2026-27139" ], "GO-2026-4603": [ "BIT-golang-2026-27142", "CVE-2026-27142" ], "GO-2026-4864": [ "BIT-golang-2026-32282", "CVE-2026-32282" ], "GO-2026-4865": [ "BIT-golang-2026-32289", "CVE-2026-32289" ], "GO-2026-4869": [ "BIT-golang-2026-32288", "CVE-2026-32288" ], "GO-2026-4870": [ "BIT-golang-2026-32283", "CVE-2026-32283" ], "GO-2026-4918": [ "BIT-golang-2026-33814", "CVE-2026-33814" ], "GO-2026-4946": [ "BIT-golang-2026-32281", "CVE-2026-32281" ], "GO-2026-4947": [ "BIT-golang-2026-32280", "CVE-2026-32280" ], "GO-2026-4970": [ "BIT-golang-2026-39822", "CVE-2026-39822" ], "GO-2026-4971": [ "BIT-golang-2026-39836", "CVE-2026-39836" ], "GO-2026-4976": [ "BIT-golang-2026-39825", "CVE-2026-39825" ], "GO-2026-4977": [ "BIT-golang-2026-42499", "CVE-2026-42499" ], "GO-2026-4980": [ "BIT-golang-2026-39826", "CVE-2026-39826" ], "GO-2026-4981": [ "BIT-golang-2026-33811", "CVE-2026-33811" ], "GO-2026-4982": [ "BIT-golang-2026-39823", "CVE-2026-39823" ], "GO-2026-4986": [ "BIT-golang-2026-39820", "CVE-2026-39820" ], "GO-2026-5024": [ "CVE-2026-39824" ], "GO-2026-5037": [ "BIT-golang-2026-27145", "CVE-2026-27145" ], "GO-2026-5038": [ "BIT-golang-2026-42504", "CVE-2026-42504" ], "GO-2026-5039": [ "BIT-golang-2026-42507", "CVE-2026-42507" ], "GO-2026-5856": [ "BIT-golang-2026-42505", "CVE-2026-42505" ], "GO-2026-5970": [ "CVE-2026-56852" ] }, "cross_scanner_correlation": { "only_osv": [ "GO-2026-4601", "GO-2026-4602", "GO-2026-4603", "GO-2026-4864", "GO-2026-4865", "GO-2026-4869", "GO-2026-4870", "GO-2026-4918", "GO-2026-4946", "GO-2026-4947", "GO-2026-4970", "GO-2026-4971", "GO-2026-4976", "GO-2026-4977", "GO-2026-4980", "GO-2026-4981", "GO-2026-4982", "GO-2026-4986", "GO-2026-5037", "GO-2026-5038", "GO-2026-5039", "GO-2026-5856" ], "only_trivy": [], "intersection_ids": [ "CVE-2026-39824", "CVE-2026-56852" ] } }, "display_score": 88.0, "display_badge": "Verified" }, { "scanner_name": "trivy_image", "scanner_version": "0.71.0", "score": 100.0, "scanner_badge": "Verified", "findings": [], "execution_duration_seconds": 4.225899465382099e-05, "status": "not_applicable", "examined": { "unit": "image_targets", "count": 0 }, "metadata": { "reason": "no OCI image acquired for this artifact" }, "display_score": null, "display_badge": "not_applicable" }, { "scanner_name": "govulncheck", "scanner_version": "v1.6.0", "score": 100.0, "scanner_badge": "Verified", "findings": [], "execution_duration_seconds": 1.9066458800225519, "status": "incomplete", "examined": { "unit": "modules", "count": 0 }, "metadata": { "db": "file:///opt/govulncheck-db", "source": "go-module-proxy", "scan_mode": "source", "go_version": "go1.26.5", "scan_level": "symbol", "source_url": "https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck", "report_type": "go-reachability", "stderr_tail": "ub.com/spf13/cobra\" imported as cmdutil and not used\n/repo/tools/gendocs/main.go:64:23: undefined: cobra\n/repo/tools/gendocs/main.go:71:34: undefined: cobra\n/repo/tools/gendocs/main.go:89:18: undefined: cobra\n/repo/tools/gendocs/main.go:89:36: undefined: cobra\n/repo/tools/gendocs/main.go:90:13: undefined: cobra\n/repo/tools/gendocs/main.go:10:2: \"github.com/spf13/cobra\" imported as cmdutil and not used\n\nFor details on package patterns, see https://pkg.go.dev/cmd/go#hdr-Package_lists_and_patterns.", "vendor_mode": false, "error_message": "govulncheck emitted no SBOM block, so it loaded no packages and analyzed nothing \u2014 the zero findings in this run carry no verdict", "go_mod_present": true, "install_command": "GOTOOLCHAIN=local GOFLAGS=-mod=mod GOSUMDB=sum.golang.org GOBIN=/usr/local/bin go install golang.org/x/vuln/cmd/govulncheck@v1.6.0 # golang.org/x/vuln v1.6.0 h1:FeMO9Rm/HwyduOztbvKcOw+zvDEPr4I4aQNSfevFcKY=", "offline_db_path": "/opt/govulncheck-db", "db_last_modified": "2026-08-10T22:42:36Z", "environment_note": "govulncheck analyzed zero modules. The measured cause under --network=none is that the artifact's third-party Go dependencies cannot be resolved: dependency_resolver.py resolves npm/pip/cargo and not Go, and GOPROXY=off makes a module fetch fail fast rather than stall. Trees that DO scan offline today: stdlib-only modules, and modules that commit a vendor/ tree (which needs GOFLAGS=-mod=vendor, not -mod=readonly).", "osv_records_loaded": 0, "govulncheck_version_reported": "v1.6.0" }, "display_score": null, "display_badge": "unavailable" } ] ```