Egress traffic for integrations should be restricted to an allow‑listed set of hostnames or IP ranges. Unrestricted outbound requests increase SSRF blast radius and data exfiltration risk. Enforce DNS pinning, firewall rules, or HTTP client allow‑lists to constrain destinations.
Magento and its extensions often make outbound HTTP requests to third-party services (payment gateways, shipping APIs, email providers, update servers). If outbound traffic is unrestricted, a compromised extension or attacker could exfiltrate sensitive data to arbitrary destinations or call malicious services.
Enforcing an outbound allow-list ensures that only approved domains and services are reachable from production servers, reducing the risk of data leakage and command-and-control callbacks.
# Review firewall or egress rules
iptables -L OUTPUT
ufw status
# Expected: outbound restricted to known services only
# Search for curl/http client usage in extensions
grep -R "curl_init" app/code vendor/
grep -R "Http\\Client" app/code vendor/
# Ensure destinations match allow-listed APIs
# Outbound unrestricted
$ curl -I http://evil.example.com
HTTP/1.1 200 OK
# Store can connect anywhere → FAIL
# Outbound restricted by firewall
$ curl -I http://evil.example.com
curl: (7) Failed to connect
# Only allow-listed domains (e.g., PayPal, UPS) reachable → PASS