CVE-2024-7073

6.5 MEDIUM

📋 TL;DR

This CVE describes a server-side request forgery (SSRF) vulnerability in multiple WSO2 products that allows unauthenticated attackers to manipulate server-side requests. Attackers can access internal and external resources available through the network or filesystem, potentially exposing sensitive data and systems. All organizations running affected WSO2 products with SOAP admin services exposed are at risk.

💻 Affected Systems

Products:
  • WSO2 API Manager
  • WSO2 Identity Server
  • WSO2 Enterprise Integrator
  • WSO2 Micro Integrator
  • WSO2 Streaming Integrator
Versions: Multiple versions across WSO2 product lines (specific versions detailed in vendor advisory)
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability affects SOAP admin services; products must have these services enabled and accessible.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of internal network resources, data exfiltration from backend systems, and potential lateral movement to other critical infrastructure.

🟠

Likely Case

Unauthorized access to internal APIs, metadata services, and file systems accessible from the vulnerable server, leading to data exposure.

🟢

If Mitigated

Limited impact due to network segmentation, proper input validation, and restricted server permissions.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

SSRF vulnerabilities typically have low exploitation complexity; attackers need network access to vulnerable endpoints.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Refer to vendor advisory for specific patched versions per product

Vendor Advisory: https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2024/WSO2-2024-3562

Restart Required: Yes

Instructions:

1. Review vendor advisory for affected product versions. 2. Apply recommended patches or updates. 3. Restart affected services. 4. Verify fix implementation.

🔧 Temporary Workarounds

Network Segmentation

linux

Restrict network access to SOAP admin services using firewall rules

iptables -A INPUT -p tcp --dport [SOAP_PORT] -j DROP
ufw deny [SOAP_PORT]

Input Validation

all

Implement strict input validation for SOAP requests

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate vulnerable systems
  • Deploy web application firewall (WAF) with SSRF protection rules

🔍 How to Verify

Check if Vulnerable:

Check if SOAP admin services are accessible and review version against vendor advisory

Check Version:

Check product documentation for version command (varies by WSO2 product)

Verify Fix Applied:

Verify patched version is installed and test SSRF attempts are blocked

📡 Detection & Monitoring

Log Indicators:

  • Unusual SOAP requests to admin services
  • Requests to internal IP addresses from SOAP endpoints
  • Failed SSRF attempts in application logs

Network Indicators:

  • Outbound connections from WSO2 servers to internal resources initiated by SOAP requests
  • Unusual port scanning from WSO2 servers

SIEM Query:

source="wso2-logs" AND (url="*soap*" OR method="POST") AND (dst_ip="10.*" OR dst_ip="192.168.*" OR dst_ip="172.16.*")

🔗 References

📤 Share & Export