dbcve.org
Arcgis ServerApplication · Esri

CVE-2022-38200

MEDIUM · 6.1 CVSS v3.1 Published 2022-10-25
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 cross site scripting vulnerability exists in some map service configurations of ArcGIS Server versions 10.8.1 and 10.7.1. Specifically crafted web requests can execute arbitrary JavaScript in the context of the victim's browser.

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 reflected cross-site scripting (XSS) vulnerability exists in specific map service configurations of ArcGIS Server versions 10.8.1 and 10.7.1. Attackers can inject malicious JavaScript through crafted web requests that execute within victim's browsers when they interact with affected map services.

MitigationApply the vendor patch or update to a supported ArcGIS Server version. Alternatively, review and sanitize map service configuration parameters or disable affected configurations until patching is feasible.

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.7.1= 10.8.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. Verify ArcGIS Server version
    Access the ArcGIS Server Administrator Directory (typically at https://<server>/arcgis/admin) or check the installation via the ArcGIS Server Post Installation utility. You can also query the REST endpoint: https://<server>/arcgis/rest/info
    Affected if The installed version matches exactly 10.7.1 or 10.8.1
  2. Identify published map services
    Query the ArcGIS Server Services Directory at https://<server>/arcgis/rest/services or access the Administrator Directory to list all published map services
    Affected if Map services are published and accessible via the web REST endpoint
  3. Check if map services are web-exposed
    Review network firewall rules and ArcGIS Server security configuration to determine if map service URLs are reachable from untrusted networks or the internet
    Affected if Map service REST endpoints are accessible from external or untrusted networks
  4. Inspect map service configuration parameters
    Review map service configuration files in the ArcGIS Server directory (typically in <InstallDir>/arcgis/server/usr/directories) or through the Administrator API to examine layer and service parameter settings
    Affected if Map services contain specific custom configurations or parameters that accept user input without sanitization

You are affected if you are running ArcGIS Server exactly version 10.7.1 or 10.8.1 AND have map services published with web-accessible endpoints that accept user-supplied parameters.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch or update to a supported ArcGIS Server version. Alternatively, review and sanitize map service configuration parameters or disable affected configurations until patching is feasible.

Recommended fix Moderate confidence

Upgrade to ArcGIS Server 10.9.1 or later (or the latest 11.x release) after applying the applicable security patch

  1. 1. Review Esri's official security advisories at https://www.esri.com/trust-center/security-bulletins for patch information related to CVE-2022-38200
  2. 2. Identify all ArcGIS Server deployments running versions 10.7.1 or 10.8.1 in your environment
  3. 3. Download and apply the appropriate security patch from Esri's support portal after reviewing the bulletin
  4. 4. Test the patch in a staging environment before production deployment
  5. 5. Deploy the patch to production systems
  6. 6. Verify the XSS vulnerability is remediated by reviewing the patch release notes
Caveat Review Esri's upgrade documentation for your migration path; major version upgrades may require configuration changes and downtime

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Arcgis Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38200 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2022-38200 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