Portal For ArcgisApplication · Esri

CVE-2022-38187

HIGH · 7.5 CVSS v3.1 Published 2022-08-15
Fix available
A fix is available. Upgrade to 10.9 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Prior to version 10.9.0, the sharing/rest/content/features/analyze endpoint is always accessible to anonymous users, which could allow an unauthenticated attacker to induce Esri Portal for ArcGIS to read arbitrary URLs.

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 confidence

Esri Portal for ArcGIS versions prior to 10.9.0 contain an authentication bypass in the /sharing/rest/content/features/analyze endpoint, allowing unauthenticated users to trigger server-side requests to arbitrary URLs (SSRF). This could enable attackers to probe internal services, bypass network restrictions, or conduct further reconnaissance.

MitigationUpgrade Esri Portal for ArcGIS to version 10.9.0 or later to remediate the vulnerability. If immediate upgrading is not feasible, consider restricting access to the affected endpoint at the network level or implementing WAF rules as a temporary mitigation.

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
Portal For ArcgisApplication
Affected:< 10.9

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Esri Portal for ArcGIS is installed
    Check for the presence of Esri Portal for ArcGIS installation directories and services on the server. Typically installed under C:\Program Files\ArcGIS\Portal or /opt/arcgis/portal.
    Affected if Esri Portal for ArcGIS is found on the system
  2. Determine installed Portal version
    Access the Portal Administrator Directory at https://<server>:7443/arcgis/portal/admin/info and retrieve the 'currentVersion' property from the JSON response, or check the installed version via the Portal desktop shortcut or installation logs.
    Affected if The installed version is below 10.9.0 (versions 10.8.1, 10.8, 10.7.1, etc.)
  3. Confirm the affected endpoint is accessible
    Attempt to access https://<server>:7443/sharing/rest/content/features/analyze from an unauthenticated context (incognito/private browser). The endpoint should respond with either an error or a prompt, indicating it is reachable.
    Affected if The endpoint responds to unauthenticated requests without requiring authentication credentials
  4. Test for SSRF vulnerability
    Send a crafted POST request to /sharing/rest/content/features/analyze with a 'url' parameter pointing to an internal service or loopback address (e.g., http://127.0.0.1:8080). Observe if the response indicates the server attempted to fetch the provided URL.
    Affected if The server accepts the request and attempts to process the arbitrary URL, indicating the SSRF vulnerability is present

A system is affected if it runs Esri Portal for ArcGIS version 10.9 or lower and the /sharing/rest/content/features/analyze endpoint is exposed without authentication.

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
Upgrade available Upgrade to 10.9 or later
Fixed in 10.9
Interim mitigation

Upgrade Esri Portal for ArcGIS to version 10.9.0 or later to remediate the vulnerability. If immediate upgrading is not feasible, consider restricting access to the affected endpoint at the network level or implementing WAF rules as a temporary mitigation.

Recommended fix High confidence

10.9.0 or later

  1. Download Portal for ArcGIS version 10.9.0 or later from the Esri Customer Portal
  2. Review the Esri upgrade documentation and prerequisites for your current version
  3. Plan maintenance window for the upgrade process
  4. Perform a complete backup of your Portal for ArcGIS configuration and content
  5. Run the upgrade installer on the Portal for ArcGIS server
  6. Verify the upgrade completed successfully
  7. Confirm the sharing/rest/content/features/analyze endpoint now requires authentication
Caveat Major version upgrades may require configuration changes; review Esri upgrade documentation before proceeding

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

Fix this in Portal For Arcgis Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38187 — 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-2022-38187 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