CVE-2020-36851 Details
Description
Rob--W cors-anywhere instances configured as an open proxy allow unauthenticated external users to induce the server to make HTTP requests to arbitrary targets (SSRF). Because the proxy forwards requests and headers, an attacker can reach internal-only endpoints and link-local metadata services, retrieve instance role credentials or other sensitive metadata, and interact with internal APIs and services that are not intended to be internet-facing. The vulnerability is exploitable by sending crafted requests to the proxy with the target resource encoded in the URL; many cors-anywhere deployments forward arbitrary methods and headers (including PUT), which can permit exploitation of IMDSv2 workflows as well as access to internal management APIs. Successful exploitation can result in theft of cloud credentials, unauthorized access to internal services, remote code execution or privilege escalation (depending on reachable backends), data exfiltration, and full compromise of cloud resources. Mitigation includes: restricting the proxy to trusted origins or authentication, whitelisting allowed target hosts, preventing access to link-local and internal IP ranges, removing support for unsafe HTTP methods/headers, enabling cloud provider mitigations, and deploying network-level protections.
A server-side request forgery (SSRF) vulnerability has been identified in CORS-Anywhere instances configured as open proxies. This vulnerability allows unauthenticated external users to induce the server to make HTTP requests to arbitrary targets. The issue is particularly critical when the proxy is hosted on an AWS EC2 instance, as it can be exploited to access sensitive instance metadata, including IAM role credentials, and interact with internal APIs and services that are not meant to be exposed to the internet.
To mitigate this vulnerability, CORS-Anywhere proxy instances should be configured to restrict access to trusted origins, authenticate users, whitelist allowed target hosts, and prevent access to link-local and internal IP ranges. Additionally, removing support for unsafe HTTP methods and headers, enabling cloud provider-specific mitigations, and deploying network-level protections can help secure the application.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Sep 25, 2025CISA-ADP
Assessed Sep 25, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/Rob--W/cors-anywhere/issues/152 | [email protected] | Issue TrackingTechnical DescriptionVendor |
| https://github.com/Rob--W/cors-anywhere/issues/521 | [email protected] | |
| https://github.com/Rob--W/cors-anywhere/issues/78 | [email protected] | ExploitIssue TrackingTechnical DescriptionVendor |
| https://github.com/SocketDev/security-research/security/advisories/GHSA-9wmg-93pw-fc3g | [email protected] | |
| https://www.certik.com/resources/blog/cors-anywhere-dangers-of-misconfigured-third-party-software | [email protected] | ExploitRemedyTechnical Analysis |
| https://www.vulncheck.com/advisories/rob-w-cors-anywhere-misconfigured-cors-proxy-allows-ssrf | [email protected] | AdvisoryBundle |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-918 | Server-Side Request Forgery (SSRF) | [email protected] |
| CWE-942 | Permissive Cross-domain Policy with Untrusted Domains | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| Rob--W cors-anywhere | All versions |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 8, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| May 26, 2026 | CVE Modified | [email protected] |
| Sep 26, 2025 | CVE Modified | [email protected] |
| Sep 25, 2025 | New CVE Received | [email protected] |
Volerion