Thursday, February 6, 2025
HomeCVE/vulnerabilityF5 BIG-IP SNMP Flaw Allows Attackers to Launch DoS Attacks

F5 BIG-IP SNMP Flaw Allows Attackers to Launch DoS Attacks

Published on

SIEM as a Service

Follow Us on Google News

A recently disclosed vulnerability in F5’s BIG-IP systems has raised alarm within the cybersecurity community.

The flaw, designated CVE-2025-21091, enables remote attackers to exploit SNMP configuration issues, potentially leading to Denial-of-Service (DoS) attacks on affected systems.

This vulnerability, which carries a CVSS v4.0 score of 8.7 (High), impacts the control plane of BIG-IP systems.

F5 has issued a security advisory regarding the issue, urging administrators to take immediate action to mitigate the risks.

Details of CVE-2025-21091

The vulnerability arises when SNMP v1 or v2c is disabled on a BIG-IP system. Under these circumstances, unspecified requests can cause increased memory usage on the system.

If left unaddressed, these memory resources may become fully consumed, degrading system performance until the snmpd process is manually or automatically restarted. This opens the door for remote, unauthenticated attackers to launch a DoS attack.

The issue affects the control plane of the BIG-IP system, which may, in turn, impact traffic handling on the data plane.

In essence, attackers could disrupt the operation of critical network and application traffic infrastructure.

F5 has classified this vulnerability under CWE-401: Missing Release of Memory after Effective Lifetime, highlighting the underlying memory management flaw.

Impacted Products and Fixes

The affected BIG-IP versions include:

  • 17.x: Vulnerable versions range from 17.1.0 to 17.1.1, with the fix available in version 17.1.2.
  • 16.x: Vulnerable versions range from 16.1.0 to 16.1.5, fixed via Hotfix-BIGIP-16.1.5.2.0.7.5-ENG.iso.
  • 15.x: Vulnerable versions range from 15.1.0 to 15.1.10, fixed via Hotfix-BIGIP-15.1.10.6.0.11.6-ENG.iso.

For other F5 products such as F5OS, NGINX, and Distributed Cloud services, this vulnerability does not pose a threat.

Administrators of vulnerable BIG-IP systems are advised to:

  1. Enable SNMP: Re-enable SNMP v1/v2c on their systems, as this reduces exposure to the vulnerability.
    • Use the following commands via TMOS Shell (tmsh):
modify sys snmp snmpv2c enable

modify sys snmp snmpv1 enable

save /sys config
  1. Restrict SNMP access to trusted management interfaces using firewall rules.
  2. Implement High Availability (HA): Configure BIG-IP systems in HA clustering mode to minimize the impact of potential disruptions.
  3. Apply Updates: Upgrade to the fixed versions listed in the security advisory as soon as possible.

Detected internally by F5, this vulnerability serves as a reminder of the importance of routine security checks and prompt patching.

Organizations relying on BIG-IP systems should immediately assess their deployments, implement mitigations, and apply the necessary updates to secure their infrastructure.

Investigate Real-World Malicious Links & Phishing Attacks With Threat Intelligence Lookup - Try for Free



Divya
Divya
Divya is a Senior Journalist at GBhackers covering Cyber Attacks, Threats, Breaches, Vulnerabilities and other happenings in the cyber world.

Latest articles

Abyss Locker Ransomware Attacking Critical Network Devices including ESXi servers

The Abyss Locker ransomware, a relatively new but highly disruptive cyber threat, has been...

Weaponized SVG Files With Google Drive Links Attacking Gmail, Outlook & Dropbox Users

A new wave of phishing attacks is leveraging Scalable Vector Graphics (SVG) files to...

Flesh Stealer Malware Attacking Chrome, Firefox, and Edge Users to Steal Passwords

A newly identified malware, Flesh Stealer, is rapidly emerging as a significant cybersecurity threat...

Beware of Nova Stealer Malware Sold for $50 on Hacking Forums

The cybersecurity landscape faces a new challenge with the emergence of Nova Stealer, a...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Abyss Locker Ransomware Attacking Critical Network Devices including ESXi servers

The Abyss Locker ransomware, a relatively new but highly disruptive cyber threat, has been...

Weaponized SVG Files With Google Drive Links Attacking Gmail, Outlook & Dropbox Users

A new wave of phishing attacks is leveraging Scalable Vector Graphics (SVG) files to...

Flesh Stealer Malware Attacking Chrome, Firefox, and Edge Users to Steal Passwords

A newly identified malware, Flesh Stealer, is rapidly emerging as a significant cybersecurity threat...