CVE-2024-51962
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 in ArcGIS Server allows an EDIT operation to modify column properties in a manner that could lead to SQL injection when performed by a remote authenticated user requiring elevated, non‑administrative privileges. Exploitation is restricted to users with advanced application‑specific permissions, indicating high privileges are required. Successful exploitation would have a high impact on integrity and confidentiality, with no impact on availability.
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's EDIT operation for modifying column properties. Exploitation requires a remote authenticated user with elevated, non-administrative privileges (advanced application-specific permissions). Successful exploitation allows attackers to inject malicious SQL queries, impacting integrity and confidentiality.
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.1, <= 11.3CVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/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 Server versionCheck the installed ArcGIS Server version through the ArcGIS Server Administrator Directory or the Services Directory. The version is typically displayed on the Administrator login page or can be retrieved via the /arcgis/rest/info endpoint.Affected if The installed version is between 10.9.1 and 11.3 inclusive.
-
Verify if Feature Services with editing are publishedList all published services through the ArcGIS Server Services Directory (typically at /arcgis/rest/services). Identify if any Feature Services are exposed that allow editing operations.Affected if Feature Services with the edit operation capability are enabled and publicly accessible.
-
Check for non-administrative users with elevated permissionsReview user roles and permissions in ArcGIS Server through the Administrator Directory. Specifically look for users assigned elevated application-specific privileges beyond standard viewers.Affected if Non-administrative users exist with advanced application-specific permissions that include editing capabilities on feature layers.
-
Confirm EDIT operation exposure for column propertiesInspect the REST API endpoint for feature services. The EDIT operation for modifying column properties is typically accessed through the Feature Service edit operation or individual layer endpoints.Affected if The EDIT operation endpoint for column properties is accessible to authenticated users with the required permissions.
A user is affected if they are running ArcGIS Server version 10.9.1 through 11.3 with exposed Feature Services that allow authenticated non-administrative users with elevated application-specific permissions to perform EDIT operations on column properties.
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 vendor patches for ArcGIS Server; implement parameterized queries or input validation for column property operations; restrict advanced application permissions to minimize attack surface.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51962 — 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-2024-51962 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