CVE-2024-21175

7.5 HIGH

📋 TL;DR

This vulnerability in Oracle WebLogic Server allows unauthenticated attackers with network access via HTTP to compromise the server's integrity. Attackers can create, delete, or modify critical data accessible to WebLogic Server. Affected versions are 12.2.1.4.0 and 14.1.1.0.0 of Oracle WebLogic Server.

💻 Affected Systems

Products:
  • Oracle WebLogic Server
Versions: 12.2.1.4.0 and 14.1.1.0.0
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the Core component of Oracle WebLogic Server. All deployments with affected versions are vulnerable regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of WebLogic Server data integrity - attackers could modify configuration files, deploy malicious applications, or delete critical data.

🟠

Likely Case

Unauthorized modification of application data, configuration files, or deployment of malicious components within WebLogic Server.

🟢

If Mitigated

Limited impact with proper network segmentation and access controls preventing unauthenticated HTTP access to WebLogic Server.

🌐 Internet-Facing: HIGH - Unauthenticated HTTP access makes internet-facing instances extremely vulnerable to exploitation.
🏢 Internal Only: MEDIUM - Internal instances are still vulnerable to internal attackers or compromised internal systems.

🎯 Exploit Status

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

CVSS indicates easily exploitable with no authentication required via HTTP. No public exploit code has been identified as of analysis.

🛠️ Fix & Mitigation

✅ Official Fix

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

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

Restart Required: Yes

Instructions:

1. Download appropriate patches from Oracle Support. 2. Apply patches following Oracle's patch installation procedures. 3. Restart WebLogic Server instances. 4. Verify patch application.

🔧 Temporary Workarounds

Network Access Restriction

all

Restrict HTTP access to WebLogic Server to trusted networks only

Configure firewall rules to limit access to WebLogic Server ports (typically 7001, 7002)

Load Balancer/Reverse Proxy Filtering

all

Implement request filtering at network perimeter

Configure WAF or reverse proxy to filter malicious requests

🧯 If You Can't Patch

  • Implement strict network segmentation and firewall rules to limit WebLogic Server access
  • Deploy Web Application Firewall (WAF) with rules specific to WebLogic vulnerabilities

🔍 How to Verify

Check if Vulnerable:

Check WebLogic Server version via console or command line. If version is 12.2.1.4.0 or 14.1.1.0.0, system is vulnerable.

Check Version:

java weblogic.version (from WebLogic installation directory)

Verify Fix Applied:

Verify patch application through Oracle OPatch utility and confirm version is no longer vulnerable.

📡 Detection & Monitoring

Log Indicators:

  • Unusual HTTP requests to WebLogic Server
  • Unauthorized configuration changes in server logs
  • Unexpected deployment activities

Network Indicators:

  • Unusual HTTP traffic patterns to WebLogic Server ports
  • Requests from unexpected sources

SIEM Query:

source="weblogic_server" AND (event_type="configuration_change" OR event_type="deployment") AND user="anonymous"

🔗 References

📤 Share & Export