dbcve.org
Big Ip Application Security ManagerApplication · F5

CVE-2017-6154

HIGH · 7.5 CVSS v3.0 Published 2018-03-01
Fix available
A fix is available. Upgrade to after 12.1.3.1 or later.
See remediation →
84/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
On F5 BIG-IP systems running 13.0.0, 12.1.0 - 12.1.3.1, or 11.6.1 - 11.6.2, the BIG-IP ASM bd daemon may core dump memory under some circumstances when processing undisclosed types of data on systems with 48 or more CPU cores.

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 · moderate confidence

On F5 BIG-IP systems running 13.0.0, 12.1.0-12.1.3.1, or 11.6.1-11.6.2, the BIG-IP ASM bd daemon may core dump memory when processing undisclosed types of data on systems with 48 or more CPU cores, causing a denial of service condition.

MitigationUpgrade to a patched BIG-IP version that addresses this vulnerability. For systems with 48+ CPU cores running affected versions, consider applying available F5 hotfixes or upgrading to a fixed release version.

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 Application Security ManagerApplication
Affected:>= 11.6.1, <= 11.6.2>= 12.1.0, <= 12.1.3.1= 13.0.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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/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. Identify F5 BIG-IP version
    Run 'tmsh show sys version' or check /etc/default/ssh/sshd_config for version info, or use 'bigtop -v'
    Affected if Version matches 13.0.0, 12.1.0-12.1.3.1, or 11.6.1-11.6.2 ranges
  2. Verify ASM module is enabled
    Run 'tmsh show ltm module' or check 'tmsh list asm' to confirm Application Security Manager module is loaded
    Affected if ASM module is present and enabled on the system
  3. Check system CPU core count
    Run 'tmsh show sys cpu' or 'cat /proc/cpuinfo' to count physical CPU cores
    Affected if System has 48 or more CPU cores
  4. Verify ASM bd daemon is running
    Run 'tmsh show sys process' or check process list for 'bd' daemon related to ASM
    Affected if ASM bd daemon is active on the system

System is affected if running an affected BIG-IP version (13.0.0, 12.1.0-12.1.3.1, or 11.6.1-11.6.2) with ASM module enabled on hardware with 48 or more CPU cores.

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 12.1.3.1
Interim mitigation

Upgrade to a patched BIG-IP version that addresses this vulnerability. For systems with 48+ CPU cores running affected versions, consider applying available F5 hotfixes or upgrading to a fixed release version.

Fix this in Big Ip Application Security Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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