CVE-2022-38208
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 · uneditedThere is an unvalidated redirect vulnerability in Esri Portal for ArcGIS 11 and below that may allow a remote, unauthenticated attacker to craft a URL that could redirect a victim to an arbitrary website, simplifying phishing attacks.
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 11 and below contains an unvalidated redirect vulnerability. A remote, unauthenticated attacker can craft malicious URLs that redirect victims to arbitrary external websites, enabling phishing attacks.
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<= 11.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Esri Portal for ArcGIS installationLocate Esri Portal for ArcGIS in your environment. Check for the Portal web application typically accessible on ports 7080, 7443, or configured web server ports. Look for 'Portal for ArcGIS' in installed programs or running services.Affected if Esri Portal for ArcGIS is not installed in the environment
-
Determine installed versionAccess the Portal administrative home page or check the software inventory. Compare your version against the affected range: versions 11.0 and below.Affected if Running version 11.0 or below (versions 10.x and earlier are also affected)
-
Identify redirect-capable parametersReview web access logs or intercept HTTP requests to Portal endpoints that include redirect-related parameters such as 'url', 'redirect', 'returnUrl', or 'next'. These are commonly found in login, logout, and authentication workflows.Affected if The application processes redirect parameters without validation
You are affected if Esri Portal for ArcGIS version 11.0 or below is running AND the application exposes redirect functionality that allows arbitrary external URLs to be specified.
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 · scopedImplement strict URL validation using an allowlist approach for all redirect parameters, restricting destinations to trusted domains only.
Portal for ArcGIS 11.1 or later (verify exact fixed release in Esri security bulletin)
- 1. Back up your current Portal for ArcGIS configuration and data
- 2. Review Esri's official security patches and release notes at www.esri.com for the CVE-2022-38208 fix
- 3. Download the fixed version of Portal for ArcGIS (version 11.1 or later) from Esri Customer Service or Downloads
- 4. Test the upgrade in a non-production environment before deploying
- 5. Execute the upgrade following Esri's standard upgrade documentation
- 6. Verify the open redirect vulnerability is resolved by testing crafted redirect URLs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38208 — 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-38208 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