CVE-2025-41430

7.5 HIGH

📋 TL;DR

This vulnerability in BIG-IP SSL Orchestrator allows undisclosed traffic to cause the Traffic Management Microkernel (TMM) to terminate, resulting in denial of service. It affects F5 BIG-IP systems with SSL Orchestrator enabled. Organizations using affected versions are vulnerable to service disruption.

💻 Affected Systems

Products:
  • F5 BIG-IP
Versions: Specific versions not provided in description; consult F5 advisory K000150667 for exact affected versions
Operating Systems: F5 TMOS
Default Config Vulnerable: ⚠️ Yes
Notes: Only vulnerable when SSL Orchestrator feature is enabled. Systems with SSL Orchestrator disabled are not affected.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete service outage of BIG-IP system, disrupting all traffic management and SSL processing capabilities, potentially affecting multiple downstream services.

🟠

Likely Case

Intermittent TMM crashes causing service disruptions, packet loss, and degraded performance until TMM restarts automatically.

🟢

If Mitigated

Minimal impact with proper network segmentation and traffic filtering preventing malicious packets from reaching vulnerable systems.

🌐 Internet-Facing: HIGH - BIG-IP systems are typically internet-facing load balancers and SSL terminators, making them directly accessible to attackers.
🏢 Internal Only: MEDIUM - Internal systems could still be targeted by compromised internal hosts or lateral movement attacks.

🎯 Exploit Status

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

Undisclosed traffic pattern suggests specific packet manipulation is required, but complexity appears low based on CVSS score and description.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check F5 advisory K000150667 for specific fixed versions

Vendor Advisory: https://my.f5.com/manage/s/article/K000150667

Restart Required: Yes

Instructions:

1. Review F5 advisory K000150667 for affected versions
2. Download appropriate fixed version from F5 Downloads
3. Backup current configuration
4. Install update following F5 upgrade procedures
5. Restart TMM services

🔧 Temporary Workarounds

Disable SSL Orchestrator

all

Temporarily disable SSL Orchestrator feature if not critically required

tmsh modify sys db ssl.orchestrator value disable
tmsh save sys config

Implement Traffic Filtering

all

Use iRules or network ACLs to filter suspicious traffic patterns

when CLIENT_ACCEPTED { if {[IP::addr [IP::client_addr] equals 10.0.0.0/8]} { reject } }

🧯 If You Can't Patch

  • Implement strict network segmentation to limit traffic to BIG-IP systems
  • Deploy intrusion prevention systems (IPS) to detect and block exploitation attempts

🔍 How to Verify

Check if Vulnerable:

Check if SSL Orchestrator is enabled: tmsh list sys db ssl.orchestrator

Check Version:

tmsh show sys version

Verify Fix Applied:

Verify installed version matches fixed versions in F5 advisory and SSL Orchestrator remains functional

📡 Detection & Monitoring

Log Indicators:

  • TMM process crashes in /var/log/ltm
  • High frequency of TMM restarts
  • SSL Orchestrator error messages

Network Indicators:

  • Unusual traffic patterns to SSL Orchestrator ports
  • Sudden drops in SSL handshake success rates

SIEM Query:

source="*/var/log/ltm*" AND ("TMM terminated" OR "panic" OR "segmentation fault")

🔗 References

📤 Share & Export