CVE-2024-21082

9.8 CRITICAL

📋 TL;DR

This critical vulnerability in Oracle BI Publisher allows unauthenticated attackers with network access via HTTP to completely compromise the system. It affects Oracle BI Publisher versions 7.0.0.0.0 and 12.2.1.4.0, enabling remote code execution and full system takeover.

💻 Affected Systems

Products:
  • Oracle BI Publisher
Versions: 7.0.0.0.0 and 12.2.1.4.0
Operating Systems: All supported platforms for Oracle BI Publisher
Default Config Vulnerable: ⚠️ Yes
Notes: Affects XML Services component. All deployments with these versions are vulnerable regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of Oracle BI Publisher server leading to data theft, system destruction, and lateral movement to other systems.

🟠

Likely Case

Remote code execution leading to data exfiltration, ransomware deployment, or creation of persistent backdoors.

🟢

If Mitigated

Limited impact if system is isolated behind strict network controls and authentication requirements.

🌐 Internet-Facing: HIGH - CVSS 9.8 with network access via HTTP and no authentication required makes internet-facing systems extremely vulnerable.
🏢 Internal Only: HIGH - Even internal systems are at high risk due to unauthenticated exploitation capability.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

CVSS 9.8 with 'easily exploitable' description suggests trivial exploitation. No authentication required via HTTP.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Apply patches from Oracle Critical Patch Update April 2024

Vendor Advisory: https://www.oracle.com/security-alerts/cpuapr2024.html

Restart Required: Yes

Instructions:

1. Download appropriate patch from My Oracle Support. 2. Apply patch following Oracle BI Publisher patching procedures. 3. Restart BI Publisher services. 4. Verify patch application.

🔧 Temporary Workarounds

Network Segmentation

all

Restrict network access to BI Publisher to only trusted sources

Use firewall rules to limit access to BI Publisher HTTP ports (typically 9704, 7001, or custom)

Authentication Enforcement

all

Require authentication for all BI Publisher endpoints

Configure BI Publisher security to require authentication for all services

🧯 If You Can't Patch

  • Isolate system from internet and restrict internal network access to minimum required
  • Implement web application firewall with XML parsing protection rules

🔍 How to Verify

Check if Vulnerable:

Check Oracle BI Publisher version via admin console or version files. Vulnerable if version is 7.0.0.0.0 or 12.2.1.4.0.

Check Version:

Check $ORACLE_HOME/OPatch/opatch lsinventory | grep -i 'BI Publisher'

Verify Fix Applied:

Verify patch application via Oracle OPatch utility: 'opatch lsinventory' and check for April 2024 CPU patches.

📡 Detection & Monitoring

Log Indicators:

  • Unusual XML parsing errors
  • Unauthenticated access to XML services
  • Unexpected process execution

Network Indicators:

  • HTTP requests to XML services endpoints from untrusted sources
  • Unusual outbound connections from BI Publisher server

SIEM Query:

source="bi_publisher_logs" AND (xml_parse_error OR unauthenticated_access) OR dest_ip="BI_Publisher_IP" AND http_method="POST" AND uri_contains="xml"

🔗 References

📤 Share & Export