Big Ip AnalyticsApplication · F5
CVE-2018-5505
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 versions 13.1.0 - 13.1.0.3, when ASM and AVR are both provisioned, TMM may restart while processing DNS requests when the virtual server is configured with a DNS profile and the Protocol setting is set to TCP.
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 versions 13.1.0-13.1.0.3 allows TMM (Traffic Management Module) to restart when processing DNS requests over TCP when ASM and AVR are both provisioned and the virtual server uses a DNS profile with TCP protocol.
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 AnalyticsApplication
>= 13.1.0, < 13.1.0.4
Big Ip Application Security ManagerApplication
>= 13.1.0, < 13.1.0.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check BIG-IP versionRun `tmsh show /sys version` or view the BIG-IP version in the web interface (System > Software). Compare the displayed version to the affected range 13.1.0 through 13.1.0.3.Affected if Version is between 13.1.0 and 13.1.0.3 inclusive
-
Verify ASM provisioningRun `tmsh list /sys provision asm` or check via web interface (System > Provisioning). Look for the provisioning level (nominal or dedicated).Affected if ASM is provisioned at any level (nominal, dedicated, or minimum)
-
Verify AVR provisioningRun `tmsh list /sys provision avr` or check via web interface (System > Provisioning). Look for the provisioning level (nominal or dedicated).Affected if AVR is provisioned at any level (nominal, dedicated, or minimum)
-
Identify virtual servers with DNS profiles using TCPRun `tmsh list /ltm virtual all` and review the dns-profile and profiles list for each virtual server. Check if any DNS profile has TCP enabled or if the virtual server has a tcp profile associated with DNS traffic.Affected if A virtual server is configured with a DNS profile and uses TCP (rather than UDP only) for DNS traffic
Environment is affected if running BIG-IP version 13.1.0-13.1.0.3 with both ASM and AVR provisioned and at least one virtual server using a DNS profile over TCP protocol.
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 data13.1.0.4
Upgrade BIG-IP to a version beyond 13.1.0.3, or if upgrade is not immediately feasible, consider disabling the DNS profile or using UDP instead of TCP for DNS where acceptable.
Fix this in Big Ip Analytics
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5505 — 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-5505 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