CVE-2024-25693
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 · uneditedThere is a path traversal in Esri Portal for ArcGIS versions <= 11.2. Successful exploitation may allow a remote, authenticated attacker to traverse the file system to access files or execute code outside of the intended directory.
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 confidenceA path traversal vulnerability in Esri Portal for ArcGIS versions 11.2 and earlier allows authenticated remote attackers to traverse the file system using specially crafted path sequences, potentially accessing sensitive files or achieving remote code execution outside the intended web root directory.
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<= 11.2CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Portal for ArcGIS versionAccess the Portal Administrator Directory at https://your-server:7443/arcgis/portal/admin or check the installed product version through the operating system's installed programs list. Compare against the affected version 11.2.Affected if The installed version is 11.2 or earlier.
-
Verify Portal web interface is accessibleConfirm the ArcGIS Portal web application is reachable at the standard ports (typically 7443 for HTTPS or 7080 for HTTP). Test connectivity using a web browser or curl command.Affected if The Portal web interface is exposed and reachable.
-
Check if authentication is enabled and exposedNavigate to the Portal login page (typically at /arcgis/home/ or /arcgis/portal/home/) and verify that user authentication is functional. The vulnerability requires an authenticated session.Affected if Anonymous or weak authentication is configured, allowing unauthenticated or low-privileged users to access the portal.
-
Review exposed administrative endpointsCheck for exposed administrative endpoints such as /arcgis/portal/admin, /arcgis/portal/portaladmin, or similar REST services that handle file operations or content uploads.Affected if Administrative or content management endpoints are accessible without strict access controls.
You are affected if your installed Esri Portal for ArcGIS version is 11.2 or earlier and the portal web interface is accessible to potential attackers.
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 Esri's security patch (upgrade to 11.3 or later) to remediate the path traversal vulnerability. If immediate patching is not feasible, implement strict access controls on authenticated user accounts and deploy file system monitoring to detect anomalous traversal attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25693 — 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-25693 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