dbcve.org
Arcgis ServerApplication · Esri

CVE-2024-51961

HIGH · 7.5 CVSS v3.1 Published 2025-03-03
Fix available
A fix is available. Upgrade to after 11.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
There is a local file inclusion vulnerability in ArcGIS Server 11.3 and below that may allow a remote, unauthenticated attacker to craft a URL that could potentially disclose sensitive configuration information by reading internal files from the remote server.  Due to the nature of the files accessible in this vulnerability the impact to confidentiality is High there is no impact to both integrity or 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 · high confidence

Local file inclusion vulnerability in ArcGIS Server 11.3 and below allows remote, unauthenticated attackers to craft URLs that read internal sensitive configuration files from the server filesystem. The vulnerability provides high confidentiality impact through arbitrary file disclosure.

MitigationUpgrade ArcGIS Server to a version above 11.3. Additionally, implement web application firewall rules to block path traversal patterns and restrict filesystem permissions to limit exposure.

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
Arcgis ServerApplication
Affected:>= 10.9.1, <= 11.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ArcGIS Server is installed
    Identify if the system runs Esri ArcGIS Server by checking installed software listings, service information, or consulting system documentation
    Affected if The system does not run ArcGIS Server, then this CVE does not apply
  2. Determine the installed ArcGIS Server version
    Use the ArcGIS Server Administrator Directory or check system configuration to retrieve the exact version number
    Affected if The installed version is 10.9.1, 11.0, 11.1, 11.2, or 11.3, meaning it falls within the vulnerable range
  3. Check if ArcGIS Server web services are externally accessible
    Verify whether the ArcGIS Server REST endpoints or Administrator endpoints are reachable from untrusted networks
    Affected if The server web interfaces are exposed to untrusted networks without network segmentation, increasing exploitability
  4. Verify if path traversal filtering is in place
    Inspect any web application firewall, reverse proxy, or web server configuration for rules that block path traversal patterns such as ../ sequences
    Affected if No path traversal protections exist and the server is in the affected version range, indicating potential exposure

A user is affected if ArcGIS Server version 10.9.1 through 11.3 is installed AND the web services are accessible without path traversal protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 11.3
Interim mitigation

Upgrade ArcGIS Server to a version above 11.3. Additionally, implement web application firewall rules to block path traversal patterns and restrict filesystem permissions to limit exposure.

Recommended fix Moderate confidence

ArcGIS Server 11.4 or later (verify exact version from Esri release notes)

  1. 1. Identify the current ArcGIS Server version by navigating to the ArcGIS Server Administrator Directory (e.g., https://servername:6443/arcgis/admin) and checking the version information.
  2. 2. Review the ArcGIS Server release notes and security advisories on Esri's website (www.esri.com) for CVE-2024-51961 to confirm the specific fixed version.
  3. 3. Before upgrading, perform a complete backup of the ArcGIS Server configuration, including the config-store and directories.
  4. 4. Test the upgrade in a non-production environment to verify compatibility with existing services and custom configurations.
  5. 5. Schedule a maintenance window for the production upgrade.
  6. 6. Follow Esri's official upgrade documentation for ArcGIS Server to install the fixed version (typically version 11.4 or later).
  7. 7. After upgrading, verify that the vulnerability is remediated by attempting to access known vulnerable endpoints - these attempts should fail.
  8. 8. Monitor Esri's security advisories for any subsequent patches or updates.
Caveat Review Esri upgrade documentation for potential breaking changes between 11.x versions, particularly around deprecated APIs or configuration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Arcgis Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-51961 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-51961 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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