dbcve.org
AmbariApplication · Apache

CVE-2025-23195

HIGH · 7.5 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to 2.7.9 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 XML External Entity (XXE) vulnerability exists in the Ambari/Oozie project, allowing an attacker to inject malicious XML entities. This vulnerability occurs due to insecure parsing of XML input using the `DocumentBuilderFactory` class without disabling external entity resolution. An attacker can exploit this vulnerability to read arbitrary files on the server or perform server-side request forgery (SSRF) attacks. The issue has been fixed in both Ambari 2.7.9 and the trunk branch.

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

This is an XXE (XML External Entity) injection vulnerability in Apache Ambari's Oozie integration. The vulnerability stems from insecure XML parsing where DocumentBuilderFactory is used without disabling external entity resolution, allowing attackers to inject malicious XML entities to read arbitrary server files or perform SSRF attacks.

MitigationUpgrade to Ambari 2.7.9 or later. For immediate mitigation, ensure all DocumentBuilderFactory instances disable external DTDs, entity resolution, and XInclude processing by setting appropriate security features.

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
AmbariApplication
Affected:< 2.7.9

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Apache Ambari version
    Run 'ambari-server --version' or check the Ambari server logs for the version string at startup
    Affected if The version is lower than 2.7.9 (e.g., 2.7.8, 2.7.7, etc.)
  2. Confirm Oozie integration is in use
    Check if Oozie service is configured and running within Ambari by reviewing Ambari's service definitions or by querying the Ambari API endpoint /api/v1/clusters/{cluster}/services/oozie
    Affected if Oozie service is registered and active in the Ambari cluster
  3. Locate Oozie-related XML parsing code
    Search source code or decompiled classes in the Ambari Oozie integration module for 'DocumentBuilderFactory' usage, typically found in files handling workflow or coordinator XML parsing
    Affected if DocumentBuilderFactory instantiation is found without security feature configurations
  4. Verify XML parser security hardening
    Inspect the DocumentBuilderFactory code for these method calls: setFeature('http://apache.org/xml/features/disallow-doctype-decl', true), setFeature('http://xml.org/sax/features/external-general-entities', false), setFeature('http://xml.org/sax/features/external-parameter-entities', false), or setXIncludeAware(false)
    Affected if None of these security features are configured, meaning external entities are not explicitly disabled
  5. Review XML workflow/coordinator upload endpoints
    Check Oozie workflow submission endpoints or REST APIs that accept XML payloads for XXE injection points, particularly where user-submitted XML is parsed
    Affected if The application accepts XML input without prior sanitization or secure parsing

You are affected if running Ambari version below 2.7.9 with Oozie integration enabled and the XML parser lacks explicit disabling of external entity resolution.

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.7.9 or later
Fixed in 2.7.9
Interim mitigation

Upgrade to Ambari 2.7.9 or later. For immediate mitigation, ensure all DocumentBuilderFactory instances disable external DTDs, entity resolution, and XInclude processing by setting appropriate security features.

Recommended fix High confidence

Ambari 2.7.9 or later

  1. 1. Backup the current Ambari installation, configuration, and database
  2. 2. Download Ambari 2.7.9 or later from the Apache Ambari releases page
  3. 3. Stop all Ambari services and the Ambari server
  4. 4. Upgrade the Ambari server package using your system's package manager (e.g., yum update ambari-server for RHEL/CentOS)
  5. 5. Upgrade the Ambari agents on all managed hosts (yum update ambari-agent)
  6. 6. Run ambari-server upgrade to migrate the database schema
  7. 7. Start the Ambari server and agents
  8. 8. Verify all services are running correctly and the XXE vulnerability is resolved

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

Fix this in Ambari Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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