CVE-2024-25699
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 difficult‑to‑exploit improper authentication issue in the Home application for Esri Portal for ArcGIS versions 11.2 and below on Windows and Linux, and ArcGIS Enterprise versions 11.1 and below on Kubernetes, which under unique circumstances could allow a remote, authenticated attacker with low‑privileged access to compromise the confidentiality, integrity, and availability of the software. Successful exploitation allows the attacker to cross an authentication and authorization boundary beyond their originally assigned access, resulting in a scope change.
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 confidenceImproper authentication vulnerability in the Home application of Esri Portal for ArcGIS (11.2 and below) and ArcGIS Enterprise (11.1 and below) allows a low-privileged authenticated remote attacker to bypass authorization boundaries under unique circumstances, achieving unauthorized access beyond their assigned permissions and resulting in a scope change.
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>= 10.8.1, <= 11.2<= 11.1CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 the installed product and versionAccess the ArcGIS Enterprise or Portal for ArcGIS administrative interface or check system documentation to determine the exact product (Portal for ArcGIS or ArcGIS Enterprise) and its installed version number.Affected if The installed version is Portal for ArcGIS 11.2 or below, or ArcGIS Enterprise 11.1 or below (including versions 10.8.1 through 11.2 for Portal).
-
Verify the Home application is accessibleCheck the Home application configuration in the Portal or Enterprise administrative settings to confirm it is enabled and accessible to users.Affected if The Home application is enabled and available to standard user accounts.
-
Check for low-privileged user accountsReview user role assignments in the administrative console to identify accounts assigned to low-privilege roles such as Viewer, User, or basic member roles.Affected if Low-privileged user accounts exist in the system.
-
Audit user permission assignmentsReview the permission configuration for low-privileged roles to determine if they have been granted access beyond their intended scope, particularly checking for unexpected access to administrative or privileged features.Affected if Low-privileged accounts have permissions that exceed their assigned role boundaries.
A user is affected if they are running Portal for ArcGIS 11.2 or below or ArcGIS Enterprise 11.1 or below, and low-privileged authenticated users can access the Home application and have achieved permissions beyond their assigned role.
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 · scopedApply vendor patches by upgrading Portal for ArcGIS to version 11.3 or later, and ArcGIS Enterprise on Kubernetes to version 11.2 or later. Alternatively, restrict low-privileged user access to the Home application until patches are applied.
Portal for ArcGIS: upgrade to 11.3 or later; ArcGIS Enterprise: upgrade to 11.2 or later
- Identify the current Portal for ArcGIS and ArcGIS Enterprise versions in your environment using the ArcGIS Administrator or enterprise portal administration.
- For Portal for ArcGIS: Upgrade to version 11.3 or later (the first release above the affected 11.2)
- For ArcGIS Enterprise: Upgrade to version 11.2 or later (the first release above the affected 11.1)
- Review Esri's upgrade documentation and pre-upgrade checklist before initiating the upgrade
- Schedule a maintenance window and perform a full backup of your deployment
- Test the upgrade in a non-production environment before applying to production
- After upgrade, verify the Home application functionality and confirm the authentication boundary issue is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25699 — 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-25699 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