Ameeba Exploit Tracker

Tracking CVEs, exploits, and zero-days for defensive cybersecurity research.

Ameeba Blog Search
TRENDING · 1 WEEK
Attack Vector
Vendor
Severity

CVE-2025-36525: Undisclosed Requests Leading to Termination of TMM in BIG-IP APM Virtual Server

Views: 21
Ameeba Chat Store screens
Download Ameeba Chat

Overview

CVE-2025-36525 is a high-severity vulnerability discovered in the BIG-IP Access Policy Manager (APM) virtual server when configured to use a PingAccess profile. This vulnerability can lead to termination of the Traffic Management Microkernel (TMM), potentially disrupting the service and possibly leading to system compromise or data leakage. This is a critical concern for organizations using the affected software versions, and an immediate patch is recommended.

Vulnerability Summary

CVE ID: CVE-2025-36525
Severity: High (7.5 CVSS Score)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Potential system compromise or data leakage

Affected Products

Ameeba Chat Icon Escape the Surveillance Era

Most apps won’t tell you the truth.
They’re part of the problem.

Phone numbers. Emails. Profiles. Logs.
It’s all fuel for surveillance.

Ameeba Chat gives you a way out.

  • • No phone number
  • • No email
  • • No personal info
  • • Anonymous aliases
  • • End-to-end encrypted

Chat without a trace.

Product | Affected Versions

BIG-IP APM | All versions using a PingAccess profile

How the Exploit Works

The vulnerability arises from the handling of undisclosed requests by the BIG-IP APM when configured to use a PingAccess profile. A malicious actor can exploit this vulnerability by sending undisclosed requests to the server. These requests cause the Traffic Management Microkernel (TMM) to terminate, potentially disrupting the service, and opening the door for system compromise or data leakage.

Conceptual Example Code

Below is a conceptual example of how the vulnerability might be exploited. This is a sample HTTP request, which simulates the undisclosed request that triggers the vulnerability.

POST /undisclosed/request HTTP/1.1
Host: vulnerable.example.com
Content-Type: application/json
{ "malicious_request": "Undisclosed request causing TMM termination" }

Mitigation and Patching Guidance

The best mitigation against this vulnerability is to apply the patch provided by the vendor. If this is not immediately possible, using a Web Application Firewall (WAF) or Intrusion Detection System (IDS) can serve as a temporary alternative for mitigating the risk associated with this vulnerability. However, these measures are not long-term solutions and should be complemented with the application of the vendor-provided patch as soon as it is feasible.

Want to discuss this further? Join the Ameeba Cybersecurity Group Chat.

Disclaimer:

The information and code presented in this article are provided for educational and defensive cybersecurity purposes only. Any conceptual or pseudocode examples are simplified representations intended to raise awareness and promote secure development and system configuration practices.

Do not use this information to attempt unauthorized access or exploit vulnerabilities on systems that you do not own or have explicit permission to test.

Ameeba and its authors do not endorse or condone malicious behavior and are not responsible for misuse of the content. Always follow ethical hacking guidelines, responsible disclosure practices, and local laws.

More posts

Ameeba Chat