dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2019-6608

MEDIUM · 5.9 CVSS v3.0 Published 2019-03-28
Fix available
A fix is available. Upgrade to after 14.0.0.2 or later.
See remediation →
68/100
Remediation priority · Elevated
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
On BIG-IP 11.5.1-11.6.3, 12.1.0-12.1.3, 13.0.0-13.1.1.1, and 14.0.0-14.0.0.2, under certain conditions, the snmpd daemon may leak memory on a multi-blade BIG-IP vCMP guest when processing authorized SNMP requests.

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

The snmpd daemon on BIG-IP contains a memory leak vulnerability that manifests when processing authorized SNMP requests specifically on multi-blade vCMP guest configurations. This memory exhaustion could lead to denial of service by depleting available memory resources on affected systems.

MitigationApply the appropriate F5 hotfix or upgrade to a fixed version (14.1.0+, 13.1.1.2+, 12.1.3.5+, or 11.6.3.2+) to remediate the memory leak in the snmpd daemon.

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.2.1, <= 11.6.3>= 12.1.0, <= 12.1.3>= 13.0.0, <= 13.1.1.1>= 14.0.0, <= 14.0.0.2
Big Ip Advanced Firewall ManagerApplication
Affected:>= 11.2.1, <= 11.6.3>= 12.1.0, <= 12.1.3>= 13.0.0, <= 13.1.1.1>= 14.0.0, <= 14.0.0.2
Big Ip Application Acceleration ManagerApplication
Affected:>= 11.2.1, <= 11.6.3>= 12.1.0, <= 12.1.3>= 13.0.0, <= 13.1.1.1>= 14.0.0, <= 14.0.0.2
Big Ip Edge GatewayWeb browser
Affected:>= 11.2.1, <= 11.6.3>= 12.1.0, <= 12.1.3>= 13.0.0, <= 13.1.1.1>= 14.0.0, <= 14.0.0.2
Big Ip Fraud Protection ServiceApplication
Affected:>= 11.2.1, <= 11.6.3>= 12.1.0, <= 12.1.3>= 13.0.0, <= 13.1.1.1>= 14.0.0, <= 14.0.0.2
Big Ip Global Traffic ManagerApplication
Affected:>= 11.2.1, <= 11.6.3>= 12.1.0, <= 12.1.3>= 13.0.0, <= 13.1.1.1>= 14.0.0, <= 14.0.0.2
Big Ip Link ControllerApplication
Affected:>= 11.2.1, <= 11.6.3>= 12.1.0, <= 12.1.3>= 13.0.0, <= 13.1.1.1>= 14.0.0, <= 14.0.0.2
Big Ip Local Traffic ManagerApplication
Affected:>= 11.2.1, <= 11.6.3>= 12.1.0, <= 12.1.3>= 13.0.0, <= 13.1.1.1>= 14.0.0, <= 14.0.0.2

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

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. Determine the installed BIG-IP version
    Run command `tmsh show /sys version` or `bigtop -v` to display the system version
    Affected if The version falls within 11.2.1-11.6.3, 12.1.0-12.1.3, 13.0.0-13.1.1.1, or 14.0.0-14.0.0.2
  2. Verify SNMP service is enabled
    Run `tmsh list /sys snmp` to view the SNMP configuration and check if the snmpd daemon is active
    Affected if SNMP is enabled and the system responds to SNMP queries
  3. Confirm vCMP guest configuration exists
    Run `tmsh show /vcmp info` or `tmsh list /sys vcmp` to check if the system is deployed as a vCMP guest
    Affected if The system is running as a vCMP guest on multi-blade hardware
  4. Check for multi-blade hardware context
    Run `tmsh show /sys hardware` to verify the underlying hardware is a multi-blade chassis (such as VIPRION)
    Affected if The vCMP guest is running on multi-blade hardware platform
  5. Monitor memory usage during SNMP operations
    Observe snmpd process memory growth over time using `tmsh show /sys process memory` or external monitoring while processing SNMP requests
    Affected if Memory usage of snmpd daemon increases continuously without releasing memory

The system is affected if it runs a vulnerable version (11.2.1-11.6.3, 12.1.0-12.1.3, 13.0.0-13.1.1.1, or 14.0.0-14.0.0.2), has SNMP enabled, and is deployed as a vCMP guest on multi-blade hardware, leading to observable memory leak in snmpd.

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
Upgrade available Upgrade to a release after 14.0.0.2
Interim mitigation

Apply the appropriate F5 hotfix or upgrade to a fixed version (14.1.0+, 13.1.1.2+, 12.1.3.5+, or 11.6.3.2+) to remediate the memory leak in the snmpd daemon.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-6608 — 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-2019-6608 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