dbcve.org
Big Ip Local Traffic ManagerApplication · F5

CVE-2018-15320

HIGH · 7.5 CVSS v3.0 Published 2018-10-31
Fix available
A fix is available. Upgrade to after 14.0.0.2 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 BIG-IP 14.0.0-14.0.0.2 or 13.0.0-13.1.1.1, undisclosed traffic patterns may lead to denial of service conditions for the BIG-IP system. The configuration which exposes this condition is the BIG-IP self IP address which is part of a VLAN group and has the Port Lockdown setting configured with anything other than "allow-all".

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 BIG-IP 14.0.0-14.0.0.2 and 13.0.0-13.1.1.1, undisclosed traffic patterns directed at a self IP address that is part of a VLAN group and has Port Lockdown configured to anything other than 'allow-all' can trigger a denial of service condition, causing the system to become unavailable.

MitigationEither change the Port Lockdown setting to 'allow-all' on affected self IPs that are members of VLAN groups, or upgrade to a patched BIG-IP version that addresses this vulnerability.

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 Local Traffic ManagerApplication
Affected:>= 13.0.0, <= 13.1.1.1>= 14.0.0, <= 14.0.0.2
Big Ip Advanced Firewall ManagerApplication
Affected:>= 13.0.0, <= 13.1.1.1>= 14.0.0, <= 14.0.0.2
Big Ip Application Acceleration ManagerApplication
Affected:>= 13.0.0, <= 13.1.1.1>= 14.0.0, <= 14.0.0.2
Big Ip AnalyticsApplication
Affected:>= 13.0.0, <= 13.1.1.1>= 14.0.0, <= 14.0.0.2
Big Ip Access Policy ManagerApplication
Affected:>= 13.0.0, <= 13.1.1.1>= 14.0.0, <= 14.0.0.2
Big Ip Protocol Security ModulePlugin / extension
Affected:>= 13.0.0, <= 13.1.1.1>= 14.0.0, <= 14.0.0.2
Big Ip Domain Name SystemApplication
Affected:>= 13.0.0, <= 13.1.1.1>= 14.0.0, <= 14.0.0.2
Big Ip Edge GatewayWeb browser
Affected:>= 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
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. Check BIG-IP product version
    Run 'tmsh show sys version' or view the web UI at System > Software Management > Images to identify the installed BIG-IP version
    Affected if Version is 13.0.0-13.1.1.1 or 14.0.0-14.0.0.2
  2. Identify self IP addresses
    Run 'tmsh list net self all' or view Network > Self IPs in the web UI to list all configured self IP addresses
    Affected if Self IPs exist on the system
  3. Determine if self IPs are members of VLAN groups
    For each self IP, examine the 'vlan' or 'vlan-group' field in the output from 'tmsh list net self <self-ip-name>' to see if it belongs to a VLAN or VLAN group
    Affected if Any self IP has a 'vlan-group' assigned (not just a single 'vlan')
  4. Check Port Lockdown setting on self IPs in VLAN groups
    Run 'tmsh list net self all' and look for the 'port-lockdown' field for each self IP that is part of a VLAN group
    Affected if Port Lockdown is set to anything other than 'allow-all' (such as 'allow-default' or 'allow-none')

System is affected only if running a vulnerable version AND has at least one self IP that is a member of a VLAN group with Port Lockdown configured to something other than 'allow-all'.

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

Either change the Port Lockdown setting to 'allow-all' on affected self IPs that are members of VLAN groups, or upgrade to a patched BIG-IP version that addresses this vulnerability.

Fix this in Big Ip Local Traffic Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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