CVE-2025-21549

7.5 HIGH

📋 TL;DR

This vulnerability allows unauthenticated attackers to cause a denial of service (DoS) on Oracle WebLogic Server 14.1.1.0.0 by sending specially crafted HTTP/2 requests. The attack can crash or hang the server, making it unavailable to legitimate users. Organizations running the affected WebLogic version are at risk.

💻 Affected Systems

Products:
  • Oracle WebLogic Server
Versions: 14.1.1.0.0
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the Core component. HTTP/2 protocol support is required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete service outage of WebLogic Server, disrupting all applications and services hosted on it, potentially for extended periods if attacks are repeated.

🟠

Likely Case

Service disruption causing application downtime, user complaints, and potential business impact until the server is restarted.

🟢

If Mitigated

Limited impact with proper network segmentation and rate limiting, though service could still be temporarily affected.

🌐 Internet-Facing: HIGH - Unauthenticated network access via HTTP/2 makes internet-facing servers extremely vulnerable to DoS attacks.
🏢 Internal Only: MEDIUM - Internal attackers or compromised internal systems could still exploit this, but attack surface is reduced compared to internet-facing deployments.

🎯 Exploit Status

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

Described as 'easily exploitable' in the advisory. No authentication required and network access via HTTP/2 is sufficient.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Apply the January 2025 Critical Patch Update

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

Restart Required: Yes

Instructions:

1. Download the January 2025 Critical Patch Update from Oracle Support. 2. Apply the patch to WebLogic Server 14.1.1.0.0. 3. Restart the WebLogic Server instances. 4. Verify the patch is applied successfully.

🔧 Temporary Workarounds

Disable HTTP/2 Protocol

all

Temporarily disable HTTP/2 support to prevent exploitation via this vector

Edit WebLogic configuration to disable HTTP/2 protocol support

Network Access Controls

all

Restrict network access to WebLogic Server management ports

Configure firewall rules to limit access to trusted IP addresses only

🧯 If You Can't Patch

  • Implement strict network segmentation and firewall rules to limit access to WebLogic servers
  • Deploy Web Application Firewall (WAF) with HTTP/2 protocol anomaly detection and rate limiting

🔍 How to Verify

Check if Vulnerable:

Check WebLogic Server version using the WebLogic console or command line. If version is exactly 14.1.1.0.0, the system is vulnerable.

Check Version:

java weblogic.version

Verify Fix Applied:

Verify that the January 2025 Critical Patch Update has been applied and check that the server version shows as patched in the Oracle advisory.

📡 Detection & Monitoring

Log Indicators:

  • Multiple connection resets or server crashes in WebLogic logs
  • Unusual HTTP/2 traffic patterns or malformed requests

Network Indicators:

  • Spike in HTTP/2 traffic to WebLogic servers
  • Multiple TCP RST packets from WebLogic ports

SIEM Query:

source="weblogic" AND (event_type="CRASH" OR event_type="HANG" OR message="connection reset")

🔗 References

📤 Share & Export