Big Ip Local Traffic ManagerApplication · F5
CVE-2017-6135
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 · uneditedIn F5 BIG-IP LTM, AAM, AFM, Analytics, APM, ASM, DNS, GTM, Link Controller, PEM and WebSafe software version 13.0.0, a slow memory leak as a result of undisclosed IPv4 or IPv6 packets sent to BIG-IP management port or self IP addresses may lead to out of memory (OOM) conditions.
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 confidenceMemory leak vulnerability in F5 BIG-IP software where undisclosed IPv4 or IPv6 packets sent to the management port or self IP addresses cause progressive memory exhaustion, eventually leading to out of memory (OOM) conditions and potential system failure.
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
= 13.0.0
Big Ip Application Acceleration ManagerApplication
= 13.0.0
Big Ip Advanced Firewall ManagerApplication
= 13.0.0
Big Ip AnalyticsApplication
= 13.0.0
Big Ip Access Policy ManagerApplication
= 13.0.0
Big Ip Application Security ManagerApplication
= 13.0.0
Big Ip DnsApplication
= 13.0.0
Big Ip Global Traffic ManagerApplication
= 13.0.0CVSS 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.
-
Identify installed BIG-IP versionRun command to display the system version, such as 'tmsh show /sys version' or check /VERSION fileAffected if The installed version is exactly 13.0.0 (this is the only affected version)
-
Verify management port network exposureCheck the management interface configuration and firewall rules to determine if the management port (port 443/80) is accessible from untrusted networksAffected if The management port is exposed to untrusted networks and the version is 13.0.0
-
Identify self IP addresses and accessibilityList configured self IP addresses using tmsh command such as 'tmsh list /net self' and review network accessibilityAffected if Self IP addresses are configured and reachable from untrusted networks while running version 13.0.0
-
Monitor memory usage patternsTrack memory utilization over time using 'tmsh show /sys memory' or equivalent system monitoring toolsAffected if Progressive memory exhaustion is observed without other explanatory causes, and the system is at version 13.0.0
A system is affected only if it is running BIG-IP version 13.0.0 AND has its management port or self IP addresses accessible from network locations where undisclosed IPv4/IPv6 packets could be received.
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 dataRestrict access to the management port and self IP addresses to trusted networks only; monitor memory usage; apply F5 vendor patches or upgrade to a patched version (13.1.0+ or later hotfix).
Fix this in Big Ip Local Traffic Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6135 — 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-2017-6135 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