CVE-2022-38203
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 · uneditedProtections against potential Server-Side Request Forgery (SSRF) vulnerabilities in Esri Portal for ArcGIS versions 10.8.1 and below were not fully honored and may allow a remote, unauthenticated attacker to forge requests to arbitrary URLs from the system, potentially leading to network enumeration or reading from hosts inside the network perimeter, a different issue than CVE-2022-38211 and CVE-2022-38212.
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 confidenceEsri Portal for ArcGIS versions 10.8.1 and below contains incomplete SSRF protections, allowing unauthenticated remote attackers to forge HTTP requests from the server to arbitrary URLs. This can enable network enumeration and access to internal resources behind the firewall that the server can reach.
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.8.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Esri Portal for ArcGIS versionAccess the ArcGIS Portal Administrator Directory (typically at https://[hostname]:7443/arcgis/portal/admin) and navigate to System > Properties > Show Advanced Options, or check the installation via the setup logs and program files. Alternatively, query the portal's REST API endpoint at /arcgis/sharing/rest/portals/self for the 'currentVersion' or 'portalVersion' property.Affected if The installed version is 10.8.1 or any version lower than 10.9.1
-
Determine if the server has outbound network accessReview firewall rules and network configuration on the Esri Portal host to confirm whether the application is permitted to initiate outbound HTTP/HTTPS connections to arbitrary network destinations.Affected if The server has unrestricted outbound internet or intranet access, allowing it to reach arbitrary URLs
-
Identify any web endpoints that accept URL or URI inputReview the Esri Portal web application's exposed endpoints, particularly any that handle external resource fetching, URL preview, or integration with external services. Check the ArcGIS Portal REST API documentation for endpoints that accept URLs as parameters.Affected if There are accessible web endpoints that accept user-supplied URLs without proper validation, which could be exploited to trigger the SSRF flaw
-
Audit recent HTTP request logs for suspicious patternsExamine web server logs (typically found in the ArcGIS Portal installation directory under /logs or /arcgis/portal/logs) for any unusual outbound requests to internal IP ranges, localhost, or unexpected external domains.Affected if There are log entries showing requests originating from the server to internal resources, localhost (127.0.0.1), or private IP ranges that were not initiated by legitimate administrative actions
The environment is affected if Esri Portal for ArcGIS version 10.8.1 or below is installed and the application has network connectivity that would allow a crafted HTTP request to reach internal resources via the vulnerable SSRF vector.
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.
From vendor dataUpgrade Esri Portal for ArcGIS to version 10.9.1 or later. As an interim control, implement strict outbound firewall rules and network segmentation to limit server connectivity to only trusted endpoints.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2022-38203 — 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-2022-38203 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