CVE-2025-1068
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 an untrusted search path vulnerability in Esri ArcGIS AllSource 1.2 and 1.3 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 AllSource, the file could execute and run malicious commands under the context of the victim. This issue is corrected in ArcGIS AllSource 1.2.1 and 1.3.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 confidenceAn untrusted search path vulnerability in Esri ArcGIS AllSource versions 1.2 and 1.3 allows a low-privileged attacker with filesystem write access to place a malicious executable in a directory within the application's search path. When a victim performs a specific action in ArcGIS AllSource, the application loads and executes the attacker's file with the victim's privileges, enabling command execution.
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= 1.2= 1.3= 3.3= 3.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed ArcGIS AllSource versionOpen ArcGIS AllSource and navigate to Help > About ArcGIS AllSource, or check the Windows Programs and Features list to view the installed version numberAffected if The version listed is exactly 1.2 or 1.3 (older versions may also be affected but the scope is 1.2-1.3 per this CVE)
-
Identify installed ArcGIS Pro versionOpen ArcGIS Pro and check Help > About ArcGIS Pro, or view the version in Windows Programs and FeaturesAffected if The version listed is exactly 3.3 or 3.4 (older versions may also be affected but the scope is 3.3-3.4 per this CVE)
-
Review directories in the application search pathExamine the PATH environment variable for the user context running ArcGIS, and check common installation directories (such as the bin folder within the ArcGIS installation directory) for directories that the application will search when loading executablesAffected if There are directories writable by low-privileged users that are included in the application search path
-
Inspect search path directories for unauthorized executablesList all executable files (.exe, .dll, .bat, .cmd) in directories within the ArcGIS application search path, paying particular attention to the installation directory and any subdirectoriesAffected if Any executable exists that was not placed there by legitimate installation or administration processes
-
Verify directory write permissionsUse icacls or Get-Acl PowerShell commands to examine write permissions on directories within the ArcGIS application search path, focusing on the installation folder and its subdirectoriesAffected if Low-privileged or non-administrative users have write access to directories in the application's search path
A user is affected if they are running ArcGIS AllSource version 1.2 or 1.3 (or ArcGIS Pro 3.3 or 3.4) and any directory in the application's search path is writable by low-privileged users, allowing potential placement of malicious executables that could be loaded during normal application operation.
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.
dbcve · scopedUpgrade to ArcGIS AllSource version 1.2.1 or 1.3.1 (or later) to apply the vendor patch. Additionally, restrict write permissions on directories in the application search path to prevent attacker placement of malicious executables.
ArcGIS AllSource 1.2.1 or 1.3.1; ArcGIS Pro - contact Esri for fixed version
- Identify which ArcGIS product (AllSource or Pro) is installed in your environment
- For ArcGIS AllSource: Upgrade to version 1.2.1 or later (1.2 users)
- For ArcGIS AllSource: Upgrade to version 1.3.1 or later (1.3 users)
- For ArcGIS Pro 3.3 and 3.4: Contact Esri customer support to verify the correct patched version or pending patch release
- After upgrading, verify the installation directory permissions to ensure only privileged administrators can write to executable paths
- Test the upgraded application to confirm normal functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1068 — 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-2025-1068 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