dbcve.org
Big Ip Local Traffic ManagerApplication · F5

CVE-2019-6629

HIGH · 7.5 CVSS v3.1 Published 2019-07-03
Fix available
A fix is available. Upgrade to after 14.1.0.5 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.1.0-14.1.0.5, undisclosed SSL traffic to a virtual server configured with a Client SSL profile may cause TMM to fail and restart. The Client SSL profile must have session tickets enabled and use DHE cipher suites to be affected. This only impacts the data plane, there is no impact to the control plane.

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 confidence

A denial of service vulnerability in BIG-IP 14.1.0-14.1.0.5 allows specially crafted SSL traffic to trigger TMM (Traffic Management Module) failure and restart when targeting virtual servers configured with Client SSL profiles that have session tickets enabled and use DHE cipher suites.

MitigationDisable session tickets in affected Client SSL profiles or remove DHE cipher suites from the cipher configuration to prevent exploitation.

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:>= 14.1.0.1, <= 14.1.0.5
Big Ip Application Acceleration ManagerApplication
Affected:>= 14.1.0.1, <= 14.1.0.5
Big Ip Advanced Firewall ManagerApplication
Affected:>= 14.1.0.1, <= 14.1.0.5
Big Ip AnalyticsApplication
Affected:>= 14.1.0.1, <= 14.1.0.5
Big Ip Access Policy ManagerApplication
Affected:>= 14.1.0.1, <= 14.1.0.5
Big Ip Application Security ManagerApplication
Affected:>= 14.1.0.1, <= 14.1.0.5
Big Ip Domain Name SystemApplication
Affected:>= 14.1.0.1, <= 14.1.0.5
Big Ip Edge GatewayWeb browser
Affected:>= 14.1.0.1, <= 14.1.0.5

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.1/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 version
    Run 'tmsh show /sys version' or 'tmsh list /sys version' to obtain the installed version
    Affected if Version is between 14.1.0.1 and 14.1.0.5 inclusive
  2. Identify Client SSL profiles
    Run 'tmsh list /ltm profile client-ssl' to list all Client SSL profiles configured on the system
    Affected if Any Client SSL profiles exist on the system
  3. Check session ticket configuration
    Examine each Client SSL profile for 'session-ticket' or 'reuse' settings by running 'tmsh list /ltm profile client-ssl <profile_name>'
    Affected if Session tickets are enabled (the profile has session ticket support turned on)
  4. Check DHE cipher suite usage
    Examine the cipher configuration in each Client SSL profile by running 'tmsh list /ltm profile client-ssl <profile_name> | grep -i cipher'
    Affected if DHE cipher suites (such as DHE-RSA, DHE-DSS, or ADH ciphers) are included in the cipher list

The system is affected if it runs BIG-IP 14.1.0.1-14.1.0.5 AND has a Client SSL profile with both session tickets enabled AND DHE cipher suites configured on a virtual server

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.1.0.5
Interim mitigation

Disable session tickets in affected Client SSL profiles or remove DHE cipher suites from the cipher configuration to prevent exploitation.

Fix this in Big Ip Local Traffic Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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