# CVE-2021-29101: ArcGIS GeoEvent Server has a Directory Traversal security vulnerability.

> Unauthenticated remote attackers can read arbitrary files on ArcGIS GeoEvent Server via directory traversal.

- **Severity:** High 8.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2021
- **Updated:** 10 Apr 2025
- **Also known as:** GHSA-7q9j-c58f-8cw5

## What is CVE-2021-29101?

CVE-2021-29101 is a high-severity path traversal vulnerability in Esri ArcGIS GeoEvent Server, published on 5 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ArcGIS GeoEvent Server versions 10.8.1 and below has a read-only directory path traversal vulnerability that could allow an unauthenticated, remote attacker to perform directory traversal attacks and read arbitrary files on the system.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2021-29101?

It affects 1 product.


Products: Esri Arcgis Geoevent Server.

## How do I fix CVE-2021-29101?

No fix has been published for CVE-2021-29101 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-29101 being exploited?

There is no known exploitation of CVE-2021-29101 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-29101 and fix it if it is affected.

What it is: CVE-2021-29101 is a high-severity path traversal vulnerability in Esri ArcGIS GeoEvent Server, published on 5 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-29101 in the wild and no public exploit code.

Affected product: Esri ArcGIS GeoEvent Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-29101/ (Markdown: https://insights.sbomify.com/CVE-2021-29101/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-29101
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-29101
- OSV: https://osv.dev/vulnerability/CVE-2021-29101

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-29101/
Summaries are generated and may contain mistakes; the official description above is the record.