dbcve.org
Portal For ArcgisApplication · Esri

CVE-2024-8148

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 unvalidated redirect vulnerability in Esri Portal for ArcGIS 11.2 and below that may allow a remote, unauthenticated attacker to craft a URL that could redirect a victim to an arbitrary website, simplifying phishing attacks.

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

Esri Portal for ArcGIS 11.2 and below contains an unvalidated redirect vulnerability where the application fails to validate the destination URL in redirect parameters. A remote, unauthenticated attacker can craft malicious URLs appearing to originate from the legitimate Esri Portal domain but redirecting to attacker-controlled phishing sites, exploiting user trust in the legitimate domain.

MitigationImplement strict allowlist-based validation for all redirect URLs, rejecting any destination that does not match trusted domains or relative paths. Alternatively, configure the web server or application to disable open redirects and use indirect references for redirect targets.

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
Portal For ArcgisApplication
Affected:= 10.8.1= 10.9.1= 11.1= 11.2

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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. Identify installed Esri Portal for ArcGIS version
    Access the ArcGIS Portal Administrator Directory or check the About page in the Portal web interface to determine the exact version number running in your environment
    Affected if The installed version is 10.8.1, 10.9.1, 11.1, or 11.2
  2. Locate redirect parameters in use
    Review application logs and traffic to identify which URL parameters handle redirection (commonly 'redirect', 'returnUrl', 'url', or similar query parameters)
    Affected if Redirect parameters are present and accessible without authentication
  3. Test redirect validation behavior
    Submit a redirect parameter value pointing to an external domain (such as http://example.com) and observe whether the application allows the redirect or rejects it
    Affected if The application permits redirects to arbitrary external domains rather than restricting to trusted/internal paths only
  4. Check web server configuration for redirect handling
    Review the web server or reverse proxy configuration (IIS, Apache, or nginx) serving Esri Portal for URL validation rules or redirect allowlist configurations
    Affected if No URL validation rules are configured or the configuration allows open redirects

You are affected if your Esri Portal for ArcGIS runs version 10.8.1, 10.9.1, 11.1, or 11.2 and allows unauthenticated redirect parameters to point to external domains without validation.

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

Implement strict allowlist-based validation for all redirect URLs, rejecting any destination that does not match trusted domains or relative paths. Alternatively, configure the web server or application to disable open redirects and use indirect references for redirect targets.

Recommended fix Moderate confidence

Portal for ArcGIS 11.3 (or latest available secure release)

  1. 1. Navigate to the Esri Support website (support.esri.com) and download the latest Portal for ArcGIS release.
  2. 2. Review the release notes or security patches for the fixed version that addresses CVE-2024-8148.
  3. 3. Back up the current Portal for ArcGIS configuration and data.
  4. 4. Install the updated version following Esri's upgrade documentation for your current version.
  5. 5. Verify the open redirect vulnerability is resolved by testing the previously vulnerable URL parameters.
Caveat Review Esri upgrade documentation for potential configuration changes or migration requirements between your current version and the target version

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

Fix this in Portal For Arcgis Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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