CVE-2021-29099
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 · uneditedA SQL injection vulnerability exists in some configurations of ArcGIS Server versions 10.8.1 and earlier. Specially crafted web requests can expose information that is not intended to be disclosed (not customer datasets). Web Services that use file based data sources (file Geodatabase or Shape Files or tile cached services) are unaffected by this issue.
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 confidenceSQL injection vulnerability in ArcGIS Server 10.8.1 and earlier allows specially crafted web requests to expose internal server information that should not be disclosed. Services using file-based data sources (file Geodatabase, Shape Files, tile cached services) are not affected.
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
- 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.
-
Determine installed ArcGIS Server versionLog into ArcGIS Server Administrator Directory or check the About page in ArcGIS Server Manager. The version is typically displayed in the product information or through the /arcgis/rest/services endpoint header.Affected if Installed version is 10.8.1 or earlier.
-
Identify published servicesAccess ArcGIS Server Manager or use the Services Directory (REST API at /arcgis/rest/services) to list all published map, feature, or geocoding services.Affected if Any services are published and running.
-
Check data source type for each serviceFor each published service, inspect its data source configuration in Manager or via the REST API. Look for whether the underlying data comes from enterprise geodatabase (SDE), database connections, or other non-file sources versus file-based sources (file geodatabase, shapefiles, tile packages).Affected if Any service uses enterprise geodatabase or direct database connections (non-file-based data sources).
-
Review service endpoint exposureVerify that service endpoints are accessible over the web via standard HTTP/HTTPS. SQL injection via web requests is only exploitable if the services are network-accessible.Affected if Services are exposed to untrusted network traffic.
The environment is affected if ArcGIS Server version is 10.8.1 or earlier AND there are published services using non-file-based data sources (enterprise geodatabase, database connections) that are network-accessible.
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 ArcGIS Server beyond version 10.8.1 to a patched version. Identify and review affected service configurations to ensure they are not vulnerable to SQL injection attacks.
- Consultation6.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29099 — 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-2021-29099 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