Ssrf Server Side in Firestore
How SSRF Manifests in Firestore
Server-Side Request Forgery (SSRF) in Firestore environments typically occurs when your application accepts user-controlled URLs and makes requests on behalf of the server, allowing attackers to access internal services, cloud metadata endpoints, or external resources. In Firestore contexts, this often manifests through:
- Document URL Injection - Accepting user-provided document paths that include malicious URLs
- Cloud Function Triggers - Firestore triggers that process external URLs from documents
- Storage URL Processing - Handling user-uploaded URLs pointing to internal services
The most dangerous Firestore-specific SSRF pattern involves the projects.firestore.v1beta1 API where attackers can craft requests to access internal Google Cloud services. For example: