Big Ip Local Traffic ManagerApplication · F5
CVE-2018-5510
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 · uneditedOn F5 BIG-IP 11.5.4 HF4-11.5.5, the Traffic Management Microkernel (TMM) may restart when processing a specific sequence of packets on IPv6 virtual servers.
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 confidenceA denial of service vulnerability in F5 BIG-IP allows remote attackers to cause the Traffic Management Microkernel (TMM) to restart by sending a specific sequence of packets to IPv6 virtual servers on affected versions 11.5.4 HF4 through 11.5.5.
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
= 11.5.4= 11.5.5
Big Ip Application Acceleration ManagerApplication
= 11.5.4= 11.5.5
Big Ip Advanced Firewall ManagerApplication
= 11.5.4= 11.5.5
Big Ip AnalyticsApplication
= 11.5.4= 11.5.5
Big Ip Access Policy ManagerApplication
= 11.5.4= 11.5.5
Big Ip Application Security ManagerApplication
= 11.5.4= 11.5.5
Big Ip Edge GatewayWeb browser
= 11.5.4= 11.5.5
Big Ip Global Traffic ManagerApplication
= 11.5.4= 11.5.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check the BIG-IP versionRun 'tmsh show /sys version' or 'bigpipe version' to retrieve the installed versionAffected if The version is 11.5.4 HF4 through 11.5.5 (or between those points in the 11.5.x line)
-
Confirm IPv6 virtual servers existRun 'tmsh list /ltm virtual' and look for virtual servers with IPv6 addresses (format: ::/0 or ::ffff:xxx.xxx.xxx.xxx)Affected if Any IPv6 virtual servers are configured on the device
-
Review TMM restart eventsCheck /var/log/ltm for 'TMM restarted' or 'critical' messages, or run 'tmsh show /sys tmm-info' to see uptimeAffected if TMM has restarted or crashed with matching timestamps to suspicious network activity
-
Check for IPv6 virtual server statisticsRun 'tmsh show /ltm virtual' and inspect traffic counters on IPv6 virtual servers for anomaliesAffected if High volume of packets to IPv6 virtual servers is observed
A user is affected if their BIG-IP version falls within 11.5.4 HF4 through 11.5.5 AND they have IPv6 virtual servers configured, as the vulnerability requires both conditions to be exploitable.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the appropriate F5 hotfix (HF) for this CVE or upgrade to a fixed version beyond 11.5.5 as specified in the F5 advisory.
Fix this in Big Ip Local Traffic Manager
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5510 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-5510 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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