CVE-2021-29102
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA Server-Side Request Forgery (SSRF) vulnerability in ArcGIS Server Manager version 10.8.1 and below may allow a remote, unauthenticated attacker to forge GET requests to arbitrary URLs from the system, potentially leading to network enumeration or facilitating other attacks.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a Server-Side Request Forgery (SSRF) vulnerability in ArcGIS Server Manager version 10.8.1 and below that allows a remote, unauthenticated attacker to craft GET requests to arbitrary URLs from the compromised server. The CVSS 9.1 rating reflects the critical severity of allowing unauthenticated attackers to bypass network boundaries, perform internal network enumeration, and potentially pivot to internal services.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.9.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate ArcGIS Server installation and versionCheck the ArcGIS Server installation directory for a version file, or access the ArcGIS Server Administrator Directory (typically at https://<server>/arcgis/admin) and retrieve the server version from the systemInfo endpoint. On Windows, also check the Windows Services panel for 'ArcGIS Server' service and its associated version information.Affected if The installed version is 10.8.1 or lower (any version below 10.9.0)
-
Verify Server Manager is exposedAttempt to access the ArcGIS Server Manager web interface, typically found at https://<server>/arcgis/manager/ or https://<server>/arcgis/manager/index.html. Check if the Manager application is accessible over the network.Affected if Server Manager is accessible without authentication or with compromised credentials, indicating the attack surface is present
-
Confirm outbound network access from serverReview network configuration or firewall rules to determine if the ArcGIS Server host can initiate outbound HTTP/HTTPS connections to arbitrary destinations. This can be verified by examining proxy settings, firewall logs, or attempting a test outbound connection from the server.Affected if The server has unrestricted outbound network access, which would allow a successful SSRF attack to reach internal resources or external targets
A user is affected if their ArcGIS Server installation is version 10.8.1 or below AND the Server Manager interface is network-accessible, allowing unauthenticated attackers to abuse the SSRF to make arbitrary GET requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.9.0
Upgrade ArcGIS Server to a version above 10.8.1 (or apply vendor-supplied patches); if immediate patching is not feasible, implement network segmentation and firewall rules to restrict outbound requests from the ArcGIS Server to internal resources.
10.9.0 or later
- 1. Review the ArcGIS Server deployment and confirm the current installed version
- 2. Back up all ArcGIS Server configurations and data before proceeding with the upgrade
- 3. Download ArcGIS Server version 10.9.0 or later from the Esri customer portal
- 4. Follow Esri's official upgrade documentation for your specific deployment scenario
- 5. Verify the upgrade was successful by checking the server version in Manager
- 6. Test that all critical map services and administrative functions are operational
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29102 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-29102 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data