Summary
Pinpoint up to version 3.1.0 contains a server-side request forgery (SSRF) issue in its webhook registration endpoint, allowing authenticated users to register internal URLs without proper validation.
By abusing alarm threshold breaches to trigger outbound POST requests, an attacker can pivot the Pinpoint server into accessing internal hosts and metadata endpoints, exposing internal network resources.
Affected context
This vulnerability appears in Pinpoint deployments that expose the webhook registration feature to authenticated users and rely on server-initiated HTTP callbacks for alarm notifications.
Risk is higher when:
- The Pinpoint server has network reachability to internal services or cloud metadata endpoints
- Webhook URLs are not constrained to trusted domains or networks
- Outbound requests are performed with elevated privileges or sensitive headers
Exploit preconditions
- Attack surface: Webhook registration endpoint and alarm-triggered callback mechanism
- Required access: Authenticated user capable of registering and managing webhooks
- Trigger point: Alarm threshold breach causes the server to issue a POST request to the attacker-controlled URL
- Why exploitation is possible: The server accepts arbitrary webhook URLs and performs HTTP requests without SSRF defenses such as URL validation, network segmentation, or strict egress controls
Why this happens
The core issue is that the webhook registration logic treats user-supplied URLs as fully trusted destinations and forwards server-originated HTTP requests to them.
This aligns with CWE-918: Server-Side Request Forgery, where an application running in a privileged network context allows an attacker to control the target of outbound requests.
Absent checks on protocol, host, IP range, or metadata endpoints, the Pinpoint server becomes an unwitting proxy into internal infrastructure.
Potential impact
- Unauthorized access to internal HTTP-based services that are not directly exposed
- Interaction with cloud provider metadata endpoints, which may disclose credentials or configuration
- Discovery of internal network structure, available services, and response behaviors
- Potential data exfiltration from internal APIs reachable by the Pinpoint server
- Use of the application server as a pivot point for broader internal network attacks
General mitigation guidance
Effective mitigation usually centers on constraining where the server can send outbound requests and reducing trust in user-provided URLs.
Common defensive patterns include:
- Enforcing strict allowlists of permitted webhook domains or IP ranges
- Validating URLs to block internal address space, link-local ranges, and metadata endpoints
- Restricting protocols to HTTPS and disallowing redirects to unvalidated targets
- Applying network-level egress controls so the application cannot reach sensitive internal services
- Running the webhook execution component with least-privilege and limited network reach
How teams detect issues like this
Detection typically involves identifying risky outbound request patterns and insecure configuration in code and infrastructure.
Useful approaches include:
- Static analysis rules that flag use of HTTP client APIs with unvalidated user-supplied URLs
- Code review checklists focusing on webhook, callback, and proxy features that originate server-side requests
- Logging and monitoring of outbound HTTP traffic to detect requests targeting internal ranges or metadata services
- Policy enforcement in CI/CD that blocks changes introducing arbitrary outbound callbacks without domain or IP constraints

