dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2019-6593

MEDIUM · 5.9 CVSS v3.0 Published 2019-02-26
Fix available
A fix is available. Upgrade to after 11.5.4 or later.
See remediation →
68/100
Remediation priority · Elevated
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 11.5.1-11.5.4, 11.6.1, and 12.1.0, a virtual server configured with a Client SSL profile may be vulnerable to a chosen ciphertext attack against CBC ciphers. When exploited, this may result in plaintext recovery of encrypted messages through a man-in-the-middle (MITM) attack, despite the attacker not having gained access to the server's private key itself. (CVE-2019-6593 also known as Zombie POODLE and GOLDENDOODLE.)

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

F5 BIG-IP virtual servers with Client SSL profiles using CBC-mode ciphers are vulnerable to a chosen ciphertext attack (Zombie POODLE/GOLDENDOODLE). An attacker performing a man-in-the-middle attack can recover plaintext from encrypted sessions by manipulating CBC ciphertexts, despite not possessing the server's private key.

MitigationDisable CBC-mode ciphers in affected Client SSL profiles and configure only AEAD ciphers (e.g., AES-GCM), or upgrade to a patched BIG-IP version.

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 Access Policy ManagerApplication
Affected:>= 11.5.1, <= 11.5.4= 11.6.1= 12.1.0
Big Ip Local Traffic ManagerApplication
Affected:>= 11.5.1, <= 11.5.4= 11.6.1= 12.1.0
Big Ip Advanced Firewall ManagerApplication
Affected:>= 11.5.1, <= 11.5.4= 11.6.1= 12.1.0
Big Ip AnalyticsApplication
Affected:>= 11.5.1, <= 11.5.4= 11.6.1= 12.1.0
Big Ip Application Security ManagerApplication
Affected:>= 11.5.1, <= 11.5.4= 11.6.1= 12.1.0
Big Ip Domain Name SystemApplication
Affected:>= 11.5.1, <= 11.5.4= 11.6.1= 12.1.0
Big Ip Edge GatewayWeb browser
Affected:>= 11.5.1, <= 11.5.4= 11.6.1= 12.1.0
Big Ip Fraud Protection ServiceApplication
Affected:>= 11.5.1, <= 11.5.4= 11.6.1= 12.1.0

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

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 `bigpipe version` to determine the installed version
    Affected if Version is 11.5.1 through 11.5.4, 11.6.1, or 12.1.0
  2. Identify Client SSL profiles
    Run `tmsh list ltm profile client-ssl` to list all configured Client SSL profiles
    Affected if Any Client SSL profiles exist on the system
  3. Inspect cipher configuration in SSL profiles
    For each profile, run `tmsh list ltm profile client-ssl <profile_name>` and examine the cipher string or ciphers field
    Affected if The cipher configuration includes CBC-mode ciphers such as AES-CBC, DES-CBC, 3DES, or RC4, or uses a default cipher group that contains CBC-mode ciphers
  4. Verify CBC ciphers are actually enabled
    Check the Client SSL profile settings for 'ciphers' and 'allow' or 'options' parameters. CBC-mode is enabled if the profile does not explicitly restrict to AEAD ciphers only (e.g., AES-GCM)
    Affected if The profile allows CBC-mode ciphers or has not been configured to restrict to AEAD ciphers only

The environment is affected if running an affected BIG-IP version (11.5.1-11.5.4, 11.6.1, or 12.1.0) and any virtual server uses a Client SSL profile with CBC-mode ciphers enabled.

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 11.5.4
Interim mitigation

Disable CBC-mode ciphers in affected Client SSL profiles and configure only AEAD ciphers (e.g., AES-GCM), or upgrade to a patched BIG-IP version.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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