CVE-2022-38211
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.9.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 · moderate confidenceEsri Portal for ArcGIS versions 10.9.1 and below contains a Server-Side Request Forgery (SSRF) vulnerability where existing protections were not fully honored, allowing a remote unauthenticated attacker to forge requests to arbitrary URLs. This could enable network enumeration or reading from internal hosts inside the network perimeter.
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.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.
-
Confirm Esri Portal for ArcGIS installationLocate the Portal for ArcGIS installation directory or check system services for the Portal component. On Windows, this is typically found under C:\Program Files\ArcGIS\Portal or /opt/arcgis/portal on Linux.Affected if The product is installed on the system
-
Identify installed Portal for ArcGIS versionAccess the ArcGIS Portal Administrator Directory (typically at https://localhost:7443/arcgis/portal/admin/system/platform) or check the About page in Portal. The version number is displayed in the product information.Affected if The installed version is 10.9.1 or below (any version <= 10.9.1)
-
Verify SSRF protection statusReview the Portal for ArcGIS security settings and proxy configuration. Access the system configuration through the Administrator Directory and examine the allowed host configurations under the proxy or sharing settings.Affected if SSRF protections exist but may not be fully enforced (the vulnerability exists in how protections are honored, not in a missing feature)
If Esri Portal for ArcGIS is installed and the version is 10.9.1 or below, the environment is affected by this SSRF vulnerability.
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 · scopedUpgrade Esri Portal for ArcGIS to version 10.9.1.1 or later, or apply the relevant patch to enforce SSRF protections properly.
Portal for ArcGIS 10.9.2 or later (or latest available ArcGIS Enterprise release)
- 1. Review Esri's official security advisories at https://www.esri.com/landing/adbersecurity/ for the specific patch addressing CVE-2022-38211
- 2. Navigate to the Esri Customer Support portal or ArcGIS Enterprise documentation for Portal for ArcGIS release notes
- 3. Download and apply the latest Portal for ArcGIS security patch or upgrade to a version newer than 10.9.1
- 4. Verify the patch was applied successfully by checking the Portal for ArcGIS administrator directory or version information
- 5. Test that the SSRF protection mechanisms are functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38211 — 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-38211 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