dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2015-5058

HIGH · 7.8 CVSS v2.0 Published 2015-08-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Memory leak in the virtual server component in F5 Big-IP LTM, AAM, AFM, Analytics, APM, ASM, GTM, Link Controller, and PEM 11.5.x before 11.5.1 HF10, 11.5.3 before HF1, and 11.6.0 before HF5, BIG-IQ Cloud, Device, and Security 4.4.0 through 4.5.0, and BIG-IQ ADC 4.5.0 allows remote attackers to cause a denial of service (memory consumption) via a large number of crafted ICMP packets.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Memory leak in the virtual server component of F5 Big-IP and BIG-IQ products allows remote attackers to cause denial of service by sending crafted ICMP packets, leading to memory consumption.

MitigationApply F5 vendor hotfixes: 11.5.1 HF10, 11.5.3 HF1, or 11.6.0 HF5 (or upgrade to later supported versions) to address the ICMP handling memory leak in the virtual server component.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Big Ip Access Policy ManagerApplication
Affected:= 11.5.1= 11.5.3= 11.6.0
Big Ip Advanced Firewall ManagerApplication
Affected:= 11.5.1= 11.5.3= 11.6.0
Big Ip AnalyticsApplication
Affected:= 11.5.1= 11.5.3= 11.6.0
Big Ip Application Acceleration ManagerApplication
Affected:= 11.5.1= 11.5.3= 11.6.0
Big Ip Application Security ManagerApplication
Affected:= 11.5.1= 11.5.3= 11.6.0
Big Ip Global Traffic ManagerApplication
Affected:= 11.5.1= 11.5.3= 11.6.0
Big Ip Link ControllerApplication
Affected:= 11.5.1= 11.5.3= 11.6.0
Big Ip Local Traffic ManagerApplication
Affected:= 11.5.1= 11.5.3= 11.6.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:N/C:N/I:N/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm F5 Big-IP product is running
    Run 'tmsh show /sys version' or 'bigpipe version' to identify the installed F5 product and version
    Affected if The system is identified as a F5 Big-IP or BIG-IQ device
  2. Check Big-IP version matches affected releases
    Examine the version output from the previous step and compare to the affected versions: 11.5.1, 11.5.3, or 11.6.0
    Affected if The installed version is exactly 11.5.1, 11.5.3, or 11.6.0
  3. Verify virtual servers are configured
    Run 'tmsh list /ltm virtual' to list all configured virtual servers on the device
    Affected if One or more virtual servers exist in the configuration
  4. Confirm virtual servers accept ICMP traffic
    Review virtual server settings via 'tmsh list /ltm virtual <name>' and check the 'ip-protocol' or ICMP-related profile settings
    Affected if Virtual servers are configured to process ICMP packets (ICMP is enabled in the virtual server or associated profile)

A system is affected if it is running F5 Big-IP version 11.5.1, 11.5.3, or 11.6.0 with at least one virtual server configured to handle ICMP traffic, as the memory leak occurs in the virtual server component when processing crafted ICMP packets.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply F5 vendor hotfixes: 11.5.1 HF10, 11.5.3 HF1, or 11.6.0 HF5 (or upgrade to later supported versions) to address the ICMP handling memory leak in the virtual server component.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-5058 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-5058 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data