dbcve.org
Arcgis AllsourceApplication · Esri

CVE-2025-1067

HIGH · 7.3 CVSS v3.1 Published 2025-02-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated

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 an untrusted search path vulnerability in Esri ArcGIS Pro 3.3 and 3.4 that may allow a low privileged attacker with write privileges to the local file system to introduce a malicious executable to the filesystem. When the victim performs a specific action using ArcGIS ArcGIS Pro, the file could execute and run malicious commands under the context of the victim. This issue is addressed in ArcGIS Pro 3.3.3 and 3.4.1.

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

Untrusted search path vulnerability in ArcGIS Pro allows a low-privileged attacker with filesystem write access to place a malicious executable that gets loaded and executed when the victim performs a specific action within the application, resulting in code execution under the victim's context.

MitigationUpgrade to ArcGIS Pro 3.3.3 or 3.4.1 per vendor advisories; also restrict filesystem write permissions for low-privileged users to prevent placement of malicious executables in accessible paths.

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 AllsourceApplication
Affected:= 1.2= 1.3
Arcgis ProApplication
Affected:= 3.3= 3.4

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Check installed version of ArcGIS Pro
    Open the application and navigate to Help > About ArcGIS Pro, or check the installed programs list in Windows Control Panel > Programs and Features. Locate the version number displayed.
    Affected if The version displayed is 3.3.x or 3.4.x (specifically 3.3, 3.4, or any 3.3.x/3.4.x version prior to the patched releases)
  2. Check installed version of ArcGIS Allsource
    Open the application and check the About dialog, or examine the installed programs list in Windows Control Panel > Programs and Features for Esri ArcGIS Allsource.
    Affected if The version displayed is 1.2 or 1.3
  3. Identify application installation directories
    Locate where ArcGIS Pro or ArcGIS Allsource is installed. Common paths include C:\Program Files\ArcGIS or C:\Program Files\Esri. Check the main application folder and subdirectories for executable files (.exe).
    Affected if The application directories are found and contain executable files that could be targeted for replacement
  4. Verify filesystem permissions on application directories
    Right-click the main ArcGIS installation folder, select Properties > Security tab. Check the permissions for Users or other low-privileged groups. Use icacls or right-click to view effective permissions.
    Affected if Low-privileged users (non-admin) have Write or Write+Execute permissions to the application installation directories or subdirectories where executables are stored

A user is affected if they have ArcGIS Pro version 3.3 or 3.4, or ArcGIS Allsource version 1.2 or 1.3 installed, AND low-privileged users have filesystem write access to application directories where executables could be placed.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to ArcGIS Pro 3.3.3 or 3.4.1 per vendor advisories; also restrict filesystem write permissions for low-privileged users to prevent placement of malicious executables in accessible paths.

Recommended fix High confidence

ArcGIS Pro 3.3.3 or 3.4.1 (depending on your current major version)

  1. 1. Identify your current ArcGIS Pro version (3.3 or 3.4) from the 'About ArcGIS Pro' dialog
  2. 2. Navigate to the Esri Customer Portal or download center to obtain the corrected version
  3. 3. Download ArcGIS Pro 3.3.3 if currently on 3.3.x, or ArcGIS Pro 3.4.1 if currently on 3.4.x
  4. 4. Run the ArcGIS Pro installer with administrator privileges
  5. 5. Follow the on-screen installation wizard to complete the upgrade
  6. 6. Launch ArcGIS Pro and verify the application starts successfully
  7. 7. Confirm the version number displays correctly in the 'About ArcGIS Pro' dialog

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

Fix this in Arcgis Allsource Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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