dbcve.org
RangerApplication · Apache

CVE-2024-45479

CRITICAL · 9.1 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to 2.5.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
SSRF vulnerability in Edit Service Page of Apache Ranger UI in Apache Ranger Version 2.4.0. Users are recommended to upgrade to version Apache Ranger 2.5.0, which fixes this 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 · high confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in the Edit Service Page of the Apache Ranger administrative web interface. An attacker could exploit this to make the Ranger server perform arbitrary requests to internal or external resources, potentially accessing internal services, cloud metadata endpoints, or bypassing network segmentation.

MitigationUpgrade Apache Ranger from version 2.4.0 to version 2.5.0 or later, which contains the fix for this SSRF vulnerability.

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
RangerApplication
Affected:>= 2.4.0, < 2.5.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Determine Apache Ranger version
    Locate the ranger-admin installation and check the version file, or query the Ranger Admin UI / login page for version information, or use the command 'ranger-admin version' if available
    Affected if The installed version is 2.4.0 or higher but lower than 2.5.0
  2. Confirm Ranger Admin web interface is accessible
    Verify network accessibility of the Ranger Admin UI (typically on port 6080) from the network segments that could be exploited
    Affected if The Ranger Admin interface is reachable from untrusted networks or the internet without proper network segmentation
  3. Identify authenticated users with Service Editor privileges
    Review Ranger user/group role assignments to determine which users have permissions to access the Edit Service functionality in the admin interface
    Affected if Any non-admin or untrusted users have been granted permissions to create or edit services, making them potential SSRF attackers
  4. Check for exposed cloud metadata endpoints
    Review network configuration to determine if internal cloud metadata services (e.g., AWS IMDS at 169.168.169.254, GCP metadata server) are reachable from the Ranger server
    Affected if The Ranger host can reach internal cloud metadata or other internal services that could be targeted via SSRF

A user is affected if they run Apache Ranger version 2.4.0 through 2.4.x with the admin web interface network-accessible to users who can access the Edit Service Page.

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.5.0 or later
Fixed in 2.5.0
Interim mitigation

Upgrade Apache Ranger from version 2.4.0 to version 2.5.0 or later, which contains the fix for this SSRF vulnerability.

Recommended fix High confidence

Apache Ranger 2.5.0

  1. Verify current Apache Ranger version is >= 2.4.0 and < 2.5.0 by checking the Ranger admin UI or running `ranger-admin --version`
  2. Stop the Apache Ranger services (ranger-admin, ranger-usersync, and any plugins)
  3. Back up the Ranger database and configuration files (including `/etc/ranger` and `/var/log/ranger`)
  4. Download Apache Ranger 2.5.0 release from the official Apache repository (https://ranger.apache.org/download.html)
  5. Upgrade Ranger by deploying the 2.5.0 binaries or rebuilding from source following the upgrade documentation
  6. Run database migration scripts if provided in the 2.5.0 release notes
  7. Start the Ranger services in the correct order: first ranger-admin, then ranger-usersync, then plugins
  8. Verify the upgrade was successful by logging into the Ranger UI and checking the version displays as 2.5.0

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

Fix this in Ranger Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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