Unauthenticated TMM crash via undisclosed SIP requests
Published May 7, 2025 · Updated May 8, 2025
NULL pointer dereference in affected F5 BIG-IP releases allows remote attackers to crash TMM through undisclosed SIP requests. F5 has not disclosed which SIP request field or TMM code path dereferences the null pointer. Exposure requires a SIP MRF ALG profile on a Message Routing virtual server; successful requests terminate TMM and interrupt traffic processing.
Summary
What happened
NULL pointer dereference in affected F5 BIG-IP releases allows remote attackers to crash TMM through undisclosed SIP requests. F5 has not disclosed which SIP request field or TMM code path dereferences the null pointer. Exposure requires a SIP MRF ALG profile on a Message Routing virtual server; successful requests terminate TMM and interrupt traffic processing.
The record
- CVE
- CVE-2025-41433
- Published
- May 7, 2025
- Updated
- May 8, 2025
- Vendor
- F5 Networks
- Product
- BIG-IP
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 7, 2025CVE publishedPublication date reported by the CVE source.
- May 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=15.1.0 <*
- Affected versionversion=16.1.0 <16.1.5
- Affected versionversion=17.1.0 <17.1.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo