dbcve.org
Arcgis EarthApplication · Esri

CVE-2021-29100

HIGH · 7.8 CVSS v3.1 Published 2021-05-05
Fix available
A fix is available. Upgrade to after 1.11.0 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
A path traversal vulnerability exists in Esri ArcGIS Earth versions 1.11.0 and below which allows arbitrary file creation on an affected system through crafted input. An attacker could exploit this vulnerability to gain arbitrary code execution under security context of the user running ArcGIS Earth by inducing the user to upload a crafted file to an affected system.

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

A path traversal vulnerability in Esri ArcGIS Earth versions 1.11.0 and below allows attackers to write files to arbitrary locations on the filesystem through crafted input. By tricking users into opening or uploading malicious files, attackers can achieve arbitrary code execution under the user's security context.

MitigationUpgrade ArcGIS Earth to a version above 1.11.0. Until then, avoid opening untrusted files or URLs from untrusted sources with ArcGIS Earth.

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 EarthApplication
Affected:<= 1.11.0

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Verify ArcGIS Earth is installed
    Check for ArcGIS Earth in the list of installed applications on the system (Control Panel > Programs and Features on Windows, or Applications folder on macOS)
    Affected if ArcGIS Earth is found installed on the system
  2. Locate the installed version number
    Open ArcGIS Earth and navigate to Help > About, or right-click the application in the Start menu and select Properties to view version information
    Affected if The displayed version is 1.11.0 or lower
  3. Confirm the version against the CVE threshold
    Compare the installed version to the affected range: any version 1.11.0 or below is vulnerable
    Affected if The installed version is 1.11.0 or any version below 1.11.0

A user is affected if Esri ArcGIS Earth version 1.11.0 or lower is installed on their system.

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.

From vendor data
Upgrade available Upgrade to a release after 1.11.0
Interim mitigation

Upgrade ArcGIS Earth to a version above 1.11.0. Until then, avoid opening untrusted files or URLs from untrusted sources with ArcGIS Earth.

Fix this in Arcgis Earth Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
33.0 hours of engineering $5,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-29100 — 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-2021-29100 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