CVE-2023-25848
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 · uneditedArcGIS Enterprise Server versions 11.0 and below have an information disclosure vulnerability where a remote, unauthorized attacker may submit a crafted query that may result in a low severity information disclosure issue. The information disclosed is limited to a single attribute in a database connection string. No business data is disclosed.
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 confidenceArcGIS Enterprise Server versions 11.0 and below contains an information disclosure vulnerability where remote, unauthenticated attackers can submit crafted queries to access a single attribute from a database connection string. The disclosure is limited in scope and does not expose business 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.8.1, <= 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 ArcGIS Enterprise Server versionAccess the ArcGIS Server Administrator Directory (e.g., https://servername:6443/arcgis/admin) and check the version under 'Platform' or 'Server' information, or run 'arcgis server version' command if availableAffected if The installed version is 10.8.1, 10.8.2, 10.9, 10.9.1, 10.9.1.1, or 11.0 (any version between 10.8.1 and 11.0 inclusive)
-
Locate the query endpointIdentify if ArcGIS Feature Service or Map Service query endpoints are exposed. Common paths include /arcgis/rest/services/ServiceName/MapServer/0/query or /arcgis/rest/services/ServiceName/FeatureServer/0/queryAffected if Any ArcGIS REST service endpoints with query capability are accessible without authentication
-
Test unauthenticated query accessSend a crafted GET request to a query endpoint without providing authentication tokens, for example: https://servername:6443/arcgis/rest/services/MyService/MapServer/0/query?where=1%3D1&returnIdsOnly=trueAffected if The server returns valid query results or error messages without requiring authentication (HTTP 200 response with data or connection string attribute leakage)
-
Check network exposureReview firewall rules, load balancer configurations, or web application firewall settings to determine if the ArcGIS REST services are accessible from untrusted networks or the internetAffected if Port 6443 (ArcGIS Server) or port 80/443 (if behind web adaptor) is exposed to unauthenticated/untrusted users
You are affected if you run ArcGIS Enterprise Server versions 10.8.1 through 11.0 AND the query interface is accessible to unauthenticated network users.
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 dataRestrict and validate query inputs on affected ArcGIS endpoints; apply vendor patches when available. Consider network-level access controls to limit exposure of the query interface to unauthorized users.
- 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-2023-25848 — 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-2023-25848 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