CVE-2022-45048: Apache Ranger code execution vulnerability in policy expressions

org.apache.ranger:ranger Updated 02 Oct 2025

Summary

06/07/2023
Yes i
High
8.8

CVE-2022-45048: Apache Ranger code execution vulnerability in policy expressions. Affects org.apache.ranger:ranger versions >= 2.3.0, < 2.4.0. Fixed in 2.4.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Apache Ranger is an open-source security framework that provides centralized security administration for Hadoop components such as HDFS, Hive, HBase, and more. It allows administrators to define and manage fine-grained policies for access control. However, a vulnerability has been discovered in Apache Ranger version 2.3.0 that allows authenticated users with appropriate privileges to create policies with expressions that can exploit a code execution vulnerability.

Vulnerability Detail

The code execution vulnerability in Apache Ranger arises from the ability of authenticated users to create policies with malicious expressions. By crafting a specific policy expression, an attacker can execute arbitrary code within the context of the Apache Ranger application. This can lead to unauthorized access, data breaches, and potential compromise of the entire Hadoop ecosystem. The vulnerability has been assigned a CVSS score of 8.8, indicating a high severity level.

How To Fix

Latest published version: 2.9.0 as of 23 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.4.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Conclusion

In conclusion, Apache Ranger version 2.3.0 is vulnerable to a code execution vulnerability that allows authenticated users to execute arbitrary code. To mitigate this risk, users should update their Apache Ranger installation to version 2.4.0 or later. For further support and assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.apache.ranger:ranger →

Share this vulnerability

FAQ

Apache Ranger is an open-source security framework that provides centralized security administration for Hadoop components.

This vulnerability allows authenticated users to execute arbitrary code within the Apache Ranger application, potentially leading to unauthorized access and compromise of the Hadoop ecosystem.

Apache Ranger version 2.3.0 is affected by this vulnerability.

To fix this vulnerability, update Apache Ranger to version 2.4.0 or later.

No specific workaround has been provided for this vulnerability. It is recommended to update to the latest version of Apache Ranger.

Related vulnerabilities

Recent vulnerabilities recorded for org.apache.ranger:ranger.

How To Fix

Latest published version: 2.9.0 as of 23 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.4.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback