Arcgis ServerApplication · Esri

CVE-2021-29107

MEDIUM · 6.1 CVSS v3.1 Published 2021-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A stored Cross Site Scripting (XXS) vulnerability in ArcGIS Server Manager version 10.8.1 and below may allow a remote unauthenticated attacker to pass and store malicious strings in the ArcGIS Server Manager application.

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 · moderate confidence

A stored Cross-Site Scripting (XSS) vulnerability in ArcGIS Server Manager versions 10.8.1 and below allows remote unauthenticated attackers to inject and persist malicious script content through unsanitized input fields. When other authenticated users access the stored content, the malicious scripts execute in their browsers, potentially enabling session hijacking, credential theft, or defacement.

MitigationApply the vendor patch for CVE-2021-29107 or upgrade ArcGIS Server to a version beyond 10.8.1; implement output encoding and input validation on all user-supplied data in the Manager interface as a defense-in-depth measure until patching is complete.

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
Arcgis ServerApplication
Affected:= 10.6.1

CVSS 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if ArcGIS Server is installed
    Locate the ArcGIS Server installation directory, typically found under C:\Program Files\ArcGIS\Server or /opt/arcgis/server, and confirm the Server folder exists. On Windows, also check Services for 'ArcGIS Server' entry.
    Affected if ArcGIS Server software is present on the system
  2. Determine the installed ArcGIS Server version
    Open the ArcGIS Server Manager interface by navigating to https://<server>:6443/arcgis/manager in a web browser, or check the version file in the installation directory. The version is typically displayed on the Manager home page or in the 'About' section.
    Affected if The installed version is 10.8.1 or below, or specifically 10.6.1 as listed in affected versions
  3. Verify Manager interface accessibility
    Confirm the ArcGIS Server Manager web interface is reachable over the network at port 6443 or 6080. Check firewall rules and IIS/web server bindings that expose the Manager URL.
    Affected if The Manager interface is accessible from the network (internal or external)
  4. Inspect for existing XSS payloads in Manager
    Log into ArcGIS Server Manager and review any user-configurable fields such as service names, site descriptions, or custom settings where input may have been persisted. Check browser developer console for any script execution errors.
    Affected if Malicious script content is found stored in Manager configuration fields, or unexpected script execution occurs when accessing Manager pages

A system is affected if ArcGIS Server version 10.8.1 or below (including 10.6.1) is installed with the Manager interface accessible, and malicious scripts have been injected into stored input fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch for CVE-2021-29107 or upgrade ArcGIS Server to a version beyond 10.8.1; implement output encoding and input validation on all user-supplied data in the Manager interface as a defense-in-depth measure until patching is complete.

Fix this in Arcgis Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-29107 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-29107 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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