CVE-2022-38205
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 · uneditedIn some non-default installations of Esri Portal for ArcGIS versions 10.9.1 and below, a directory traversal issue may allow a remote, unauthenticated attacker to traverse the file system and lead to the disclosure of sensitive data (not customer-published content).
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 confidenceA directory traversal vulnerability in Esri Portal for ArcGIS versions 10.9.1 and below allows remote unauthenticated attackers to use path traversal sequences to access files outside the web root in non-default installation configurations, leading to disclosure of sensitive system data.
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.
-
Identify installed Portal for ArcGIS versionAccess the Portal Administrator Directory at https://yourserver:7443/arcgis/portal/admin and navigate to System > Properties > Platform Info, or check the installation directory for version filesAffected if Installed version is 10.9.1 or lower
-
Determine if custom web server is configuredCheck whether a separate web server (IIS, Apache, or nginx) is installed in front of the Portal for ArcGIS, or if non-default HTTP ports/path mappings are in use beyond the default 7443 portAffected if A non-default web server configuration exists in front of the Portal
-
Inspect web server path handlingReview the web server configuration files (IIS web.config, Apache httpd.conf, or nginx.conf) for any URL rewrite rules or mappings that handle incoming requests to the Portal endpointAffected if Custom URL rewrite rules or path mappings are configured that could permit traversal sequences
-
Verify default Portal endpoint behaviorTest accessing the default Portal REST services endpoint and confirm whether the web server layer properly sanitizes path traversal sequences like ../ in requested URLsAffected if The web server layer does not block or sanitize path traversal sequences
A user is affected only if their Portal for ArcGIS version is 10.9.1 or below AND they have a non-default installation configuration (custom web server or non-standard path mappings) that allows path traversal sequences to reach outside the web root.
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 · scopedApply vendor patches for Esri Portal for ArcGIS above version 10.9.1; additionally, review non-default installation configurations and implement strict input validation on file path parameters.
Portal for ArcGIS 10.9.1 or later - upgrade to the latest available stable release (10.9.2 or later if available)
- 1. Verify current Portal for ArcGIS installation version through the Portal Administrator Directory or system information.
- 2. Schedule a maintenance window for the upgrade process.
- 3. Back up the Portal for ArcGIS configuration, content, and database before proceeding.
- 4. Download the latest Portal for ArcGIS release from the Esri Customer Care Portal or official distribution channels.
- 5. Follow Esri's standard upgrade documentation for Portal for ArcGIS, ensuring all prerequisites are met.
- 6. Run the upgrade installer and verify successful completion.
- 7. Validate that the Portal for ArcGIS services start correctly and the administrator directory is accessible.
- 8. Confirm the vulnerability is remediated by verifying the directory traversal is no longer possible.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38205 — 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-38205 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