CVE-2022-38184
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 improper access control vulnerability in Portal for ArcGIS versions 10.8.1 and below which could allow a remote, unauthenticated attacker to access an API that may induce Esri Portal for ArcGIS to read arbitrary URLs.
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 confidenceThis is an improper access control vulnerability in Portal for ArcGIS that allows a remote, unauthenticated attacker to access an API endpoint that can be induced to read arbitrary URLs. This is a Server-Side Request Forgery (SSRF) vulnerability where the lack of proper authentication controls permits external actors to force the server to make requests to attacker-controlled URLs.
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 Portal for ArcGIS versionAccess the Portal Administrator Directory at https://<server>/portal/portaladmin/ and navigate to System > Properties > Update Properties, or run the command 'portaladmin.bat -v' from the installation directory. Alternatively, check the About page in the Portal for ArcGIS website.Affected if The displayed version is 10.8.1 or any earlier version (for example, 10.8, 10.7.1, 10.6.1, etc.)
-
Verify whether unauthenticated API endpoints are reachableAttempt to access the vulnerable endpoint without providing credentials. The specific endpoint is the Share/Item API that handles URL parameters. Use a tool like curl to send a request to the Portal REST API without authentication headers.Affected if The server responds with successful HTTP status (200) and returns data without requiring login credentials, indicating the API is accessible without authentication.
-
Confirm server network exposureDetermine if the Portal for ArcGIS web server is directly accessible from untrusted networks (such as the public internet) by reviewing firewall rules, reverse proxy configurations, and network ACLs. Check if port 443 (HTTPS) or 80 (HTTP) is open to external IPs.Affected if The Portal services are exposed to the internet or untrusted networks without network-level restrictions or VPN requirements.
You are affected if your Portal for ArcGIS installation is version 10.8.1 or lower AND the server API endpoints are accessible without authentication from your network.
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 dataApply the vendor patch or upgrade Portal for ArcGIS to a version beyond 10.8.1. If immediate patching is not feasible, implement network segmentation and firewall rules to restrict outbound connections from the server to minimize SSRF impact.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38184 — 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-38184 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