Big Ip Local Traffic ManagerApplication · F5
CVE-2019-6590
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 BIG-IP LTM 13.0.0 to 13.0.1 and 12.1.0 to 12.1.3.6, under certain conditions, the TMM may consume excessive resources when processing SSL Session ID Persistence traffic.
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 confidenceF5 BIG-IP LTM versions 12.1.0-12.1.3.6 and 13.0.0-13.0.1 contain a vulnerability in the Traffic Management Microkernel (TMM) where SSL Session ID Persistence processing can cause excessive resource consumption, potentially leading to denial of service.
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.1, <= 11.6.3>= 12.1.0, <= 12.1.3.6>= 13.0.0, <= 13.0.1CVSS 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.
-
Identify the installed BIG-IP LTM versionRun `tmsh show sys version` from the command line, or view the version in the web UI under System > Software > VersionAffected if The installed version falls within 11.5.1-11.6.3, 12.1.0-12.1.3.6, or 13.0.0-13.0.1
-
Locate SSL Session ID persistence profilesRun `tmsh list ltm persistence ssl-session-id` to list any persistence profiles configured to use SSL Session ID, or inspect persistence profiles in the web UI under Local Traffic > Profiles > PersistenceAffected if Any persistence profile with SSL Session ID type is defined and active
-
Identify virtual servers using SSL Session ID persistenceRun `tmsh show ltm virtual` and cross-reference with the SSL Session ID profiles found in the previous step, or review virtual server configuration in the web UI under Local Traffic > Virtual ServersAffected if A virtual server is assigned a persistence profile that uses SSL Session ID and the version is within the affected range
-
Verify TMM resource consumptionMonitor TMM memory and CPU usage via `tmsh show sys tmm-info` or the web UI under Traffic Management > Overview > Performance, looking for unexpectedly high utilization on systems with SSL Session ID persistence enabledAffected if Excessive resource consumption is observed in TMM while processing SSL Session ID persistence
A system is affected if it runs a vulnerable BIG-IP version (11.5.1-11.6.3, 12.1.0-12.1.3.6, or 13.0.0-13.0.1) AND has SSL Session ID persistence configured on any virtual server.
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 dataUpgrade to a patched F5 BIG-IP version (12.1.3.7+ or 13.0.2+), or disable SSL Session ID persistence if not required for the application.
Fix this in Big Ip Local Traffic Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation3.0 h
- Testing2.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 $2,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6590 — 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-2019-6590 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