CVE-2021-21973

Server-Side Request Forgery (SSRF) in The vSphere Client (HTML5) contains an SSRF (Server Side Request Forgery) vulnerability due to improper validation of URLs in a vCenter Server plugin

Verified by Precogs Threat Research
Last Updated: Oct 30, 2025
Base Score
5.3MEDIUM

Executive Summary

CVE-2021-21973 is a medium severity vulnerability affecting api-security. It is classified as Server-Side Request Forgery. This vulnerability is actively being exploited in the wild.

Precogs AI Insight

"The VMware vSphere Client (HTML5) contains a Server-Side Request Forgery (SSRF) flaw due to improper validation of user-supplied URLs within a specific vCenter plugin. An unauthorized network attacker can send crafted requests to force the vCenter server to scan internal infrastructure or access restricted administrative endpoints. Precogs API Security Engine actively detects SSRF vulnerabilities by tracking unvalidated URL sinks."

Exploit Probability (EPSS)
High (90.1%)
Public POC
Available
Exploit Probability
Low (<10%)
Public POC
Actively Exploited
Affected Assets
api securityCWE-918

What is this vulnerability?

CVE-2021-21973 is categorized as a medium Server-Side Request Forgery (SSRF) flaw with a CVSS base score of 5.3. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

The vSphere Client (HTML5) contains an SSRF (Server Side Request Forgery) vulnerability due to improper validation of URLs in a vCenter Server plugin. A malicious actor with network access to port 443 may exploit this issue by sending a POST request to vCenter Server plugin leading to information disclosure. This affects: VMware vCenter Server (7.x before 7.0 U1c, 6.7 before 6.7 U3l and 6.5 before 6.5 U3n) and VMware Cloud Foundation (4.x before 4.2 and 3.x before 3.10.1.2).

This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.

Risk Assessment

MetricValue
CVSS Base Score5.3 (MEDIUM)
Vector StringCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
PublishedFebruary 24, 2021
Last ModifiedOctober 30, 2025
Related CWEsCWE-918, CWE-918

Impact on Systems

Unauthorized Data Access: Attackers can bypass authorization controls to access other users' data or administrative endpoints.

Account Takeover: Broken authentication or authorization may enable full account compromise without valid credentials.

API Abuse: Exploiting this vulnerability enables mass data harvesting or destructive operations through unprotected API endpoints.

How to Fix and Mitigate CVE-2021-21973

  1. Apply Vendor Patches Immediately: This vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog. Apply updates per vendor instructions.
  2. Verify Patch Deployment: Confirm all instances are updated using Precogs continuous monitoring.
  3. Review Audit Logs: Investigate historical access logs for indicators of compromise related to this attack surface.
  4. Implement Defense-in-Depth: Deploy WAF rules, network segmentation, and endpoint detection to limit blast radius.

Defending with Precogs AI

Precogs API Security Engine performs deep analysis of API endpoints using Code Property Graph traversal, detecting broken authentication, mass assignment, BOLA/IDOR, and SSRF vulnerabilities across REST, GraphQL, and gRPC interfaces before they reach production.

Use Precogs to continuously scan your codebase, binaries, APIs, and infrastructure for this vulnerability class and related attack patterns. Our AI-powered detection engine combines static analysis with threat intelligence to identify exploitable weaknesses before attackers do.

Start scanning with Precogs →

Vulnerability Code Signature

Attack Data Flow

StageDetail
SourceUser-supplied URL parameter
VectorServer fetches the user-controlled URL
SinkHTTP request library (e.g., fetch, axios)
ImpactAccess to internal services, metadata endpoints, or port scanning

Vulnerable Code Pattern

// ❌ VULNERABLE: Server-Side Request Forgery
app.get('/proxy', async (req, res) => {
  const targetUrl = req.query.url;
  // Taint sink: unvalidated outbound request
  const response = await fetch(targetUrl);
  res.send(await response.text());
});

Secure Code Pattern

// ✅ SECURE: Allowlist validation
const ALLOWED_DOMAINS = ['api.partner.com'];
app.get('/proxy', async (req, res) => {
  const targetUrl = new URL(req.query.url);
  
  if (!ALLOWED_DOMAINS.includes(targetUrl.hostname)) {
    return res.status(403).send("Domain not allowed");
  }
  
  // Sanitized outbound request
  const response = await fetch(targetUrl.href);
  res.send(await response.text());
});

How Precogs Detects This

Precogs API Security Engine actively detects SSRF vulnerabilities by tracking unvalidated URL sinks and enforcing strict allowlist policies.\n

Related Vulnerabilitiesvia CWE-918

CVE-2026-3543110 CRITICAL

Server-Side Request Forgery (SSRF) in Server-side request forgery (ssrf) in Microsoft Entra ID Entitlement Management allows an unauthorized attacker to perform spoofing over a network

CWE-918
CVE-2026-322109.3 CRITICAL

Server-Side Request Forgery (SSRF) in Server-side request forgery (ssrf) in Microsoft Dynamics 365 (Online) allows an unauthorized attacker to perform spoofing over a network

CWE-918
CVE-2026-3218610 CRITICAL

Server-Side Request Forgery (SSRF) in Server-side request forgery (ssrf) in Microsoft Bing allows an unauthorized attacker to elevate privileges over a network

CWE-918
CVE-2026-48740 LOW

CVE-2026-4874: Server-Side Request Forgery in Keycloak

CWE-918
CVE-2026-45287.3 HIGH

A vulnerability was determined in trueleaf ApiFlow 0.

CWE-918
CVE-2024-562796.5 MEDIUM

Server-Side Request Forgery (SSRF) — Cloud metadata access

CWE-918

Is your system affected?

Precogs AI detects CVE-2021-21973 in compiled binaries, LLMs, and application layers — even without source code access.