CVE-2022-38197
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 · uneditedEsri ArcGIS Server versions 10.9.1 and below have an unvalidated redirect issue that may allow a remote, unauthenticated attacker to phish a user into accessing an attacker controlled website via a crafted query parameter.
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 ArcGIS Server versions 10.9.1 and below contain an unvalidated redirect vulnerability where the application fails to validate redirect URLs in query parameters. A remote, unauthenticated attacker can craft malicious URLs containing a redirect parameter that will redirect victims to attacker-controlled websites, enabling phishing campaigns.
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
- 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.
-
Identify installed ArcGIS Server versionAccess the ArcGIS Server Administrator Directory (typically at https://<server>/arcgis/admin) and navigate to the 'machines' endpoint, or check the 'About' page in ArcGIS Server Manager. The version is also visible in the ArcGIS Server Manager landing page.Affected if The installed version is 10.9.1 or below, as these versions contain the unvalidated redirect vulnerability in query parameters.
-
Confirm the redirect parameter functionality existsReview the ArcGIS Server web configuration and proxy settings. The vulnerability affects redirect URLs passed through query parameters - common parameter names include 'redirect', 'url', 'returnUrl', or similar. Check if the server's proxy or web adaptor configuration handles external redirect parameters.Affected if The server handles redirect parameters in URLs without server-side validation restricting redirects to trusted domains only.
-
Examine web server access logs for redirect patternsReview logs from the web server, IIS, or Apache in front of ArcGIS Server. Search for requests containing query parameters with redirect-related names (redirect=, url=, returnUrl=, etc.) followed by external domains. Logs are typically in the 'logs' folder under the ArcGIS Server installation directory or the web server's log directory.Affected if Requests are logged containing redirect parameters pointing to untrusted or external domains, indicating the vulnerable parameter is in use.
-
Check ArcGIS Server Manager security settingsLog into ArcGIS Server Manager and navigate to Security > Settings. Examine whether there are any URL validation rules configured for redirect destinations. Also check the 'Allowed Redirect URIs' configuration if present in the OAuth or token settings.Affected if No server-side validation or allowlist of trusted redirect URLs is configured, meaning any external URL can be used as a redirect target.
The environment is affected if ArcGIS Server version 10.9.1 or below is installed AND the redirect parameter functionality is accessible without validation restricting redirects to trusted internal domains.
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 to a patched version of ArcGIS Server above 10.9.1, and/or implement server-side validation of all redirect URLs to ensure they only point to trusted, internal domains.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38197 — 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-38197 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