dbcve.org
AtlasApplication · Apache

CVE-2024-46910

HIGH · 7.1 CVSS v3.1 Published 2025-02-13
Fix available
A fix is available. Upgrade to 2.4.0 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

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
An authenticated user can perform XSS and potentially impersonate another user. This issue affects Apache Atlas versions 2.3.0 and earlier. Users are recommended to upgrade to version 2.4.0, which fixes the issue.

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 confidence

Apache Atlas 2.3.0 and earlier contains a stored or reflected Cross-Site Scripting (XSS) vulnerability that allows an authenticated user to inject malicious scripts into web pages viewed by other users. Since the vulnerability can lead to user impersonation, it likely involves theft of session tokens or authentication cookies via the injected script.

MitigationUpgrade Apache Atlas to version 2.4.0 or later. Prior to production deployment, test the upgrade in a staging environment to ensure compatibility with existing data pipelines and integrations.

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
AtlasApplication
Affected:>= 2.0.0, < 2.4.0

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/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 Apache Atlas version
    Check the installed Apache Atlas version using the Atlas web UI (typically in the About or Settings section), or check the package/version file in the Atlas installation directory, or query the Atlas REST API endpoint if available.
    Affected if The installed version is 2.0.0 through 2.3.0 inclusive (any version >= 2.0.0 and < 2.4.0).
  2. Confirm web interface is enabled
    Verify that the Apache Atlas web application (UI) is accessible and running. This is typically hosted on port 21000 or similar depending on configuration.
    Affected if The Atlas web interface is accessible and the application is actively serving HTTP requests.
  3. Verify authentication is configured
    Check whether Atlas is configured with authentication (either internal or external LDAP/SSO). Review the Atlas application properties file (atlas-application.properties) for authentication-related settings.
    Affected if Authentication is enabled and users can log in to the Atlas web interface, as the XSS vulnerability affects authenticated users.

Your environment is affected if you are running Apache Atlas version 2.0.0 through 2.3.0 with the web interface and authentication enabled, allowing authenticated users to access the application.

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
Upgrade available Upgrade to 2.4.0 or later
Fixed in 2.4.0
Interim mitigation

Upgrade Apache Atlas to version 2.4.0 or later. Prior to production deployment, test the upgrade in a staging environment to ensure compatibility with existing data pipelines and integrations.

Recommended fix High confidence

2.4.0

  1. Download Apache Atlas version 2.4.0 from the official Apache Atlas release repository (https://atlas.apache.org/downloads.html)
  2. Review the Apache Atlas 2.4.0 upgrade guide in the official documentation
  3. Backup current Atlas data and configurations
  4. Install or upgrade to Apache Atlas 2.4.0 following the standard upgrade procedure
  5. Verify the XSS vulnerability is resolved by testing the affected functionality
  6. Deploy to production after confirming the fix works in non-production

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

Fix this in Atlas Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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 locally
dbcve dependency scanner

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