CVE-2020-36851: Rob--W cors-anywhere Misconfigured CORS Proxy Allows SSRF
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.
Security readout for executives and security teams
Plain-English summary
CVE-2020-36851 is a dangerous misconfiguration risk in public cors-anywhere proxy deployments. If exposed as an open proxy, outsiders can make the server contact internal systems or cloud metadata services. That can expose credentials and sensitive internal APIs, potentially leading to broader cloud compromise.
Executive priority
Treat as urgent for any public deployment. Prioritize cloud-hosted proxies because credential exposure can escalate from one service to wider environment compromise. If not externally reachable or not deployed, priority is lower.
Technical view
Open Rob--W cors-anywhere instances can enable unauthenticated SSRF because the proxy forwards attacker-directed requests and headers to arbitrary targets. The advisory describes access to internal-only endpoints, link-local metadata services, and unsafe methods/headers that may support IMDSv2-related abuse. Impact depends on reachable backends and cloud permissions.
Likely exposure
Organizations are exposed if they run cors-anywhere as an internet-accessible open proxy, especially in cloud environments with metadata services or internal APIs reachable from the proxy host.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation is network-accessible and unauthenticated when the proxy is open, but real impact depends on deployment configuration and reachable internal services.
Researcher notes
Evidence identifies a misconfiguration-driven SSRF class rather than a named patched version. Validate exposure by configuration and network reachability, not only package presence. Avoid assuming every cors-anywhere install is vulnerable without open-proxy behavior.
Mitigation direction
Restrict proxy use to trusted origins or authenticated users.
Whitelist allowed destination hosts instead of allowing arbitrary targets.
Block access to link-local, private, and internal IP ranges.
Disable unsafe HTTP methods and forwarded headers where not required.
Apply cloud metadata-service protections recommended by the cloud provider.
Check upstream and advisory sources for current vendor guidance.
Validation and detection
Inventory internet-facing cors-anywhere deployments and package usage.
Confirm whether the proxy accepts unauthenticated external requests.
Verify destination allowlists and private-address blocking are enforced.
Review whether sensitive headers and unsafe methods are forwarded.
Check cloud logs for metadata-service and internal API access from proxy hosts.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-918 · source CWE mapping
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Permissive Cross-domain Security Policy with Untrusted Domains
Permissive Cross-domain Security Policy with Untrusted Domains represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.