dbcve.org
Ssl OrchestratorApplication · F5

CVE-2019-6627

MEDIUM · 5.9 CVSS v3.0 Published 2019-07-03
Fix available
A fix is available. Upgrade to 14.1.0.6 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 F5 SSL Orchestrator 14.1.0-14.1.0.5, on rare occasions, specific to a certain race condition, TMM may restart when SSL Forward Proxy enforces the bypass action for an SSL Orchestrator transparent virtual server with SNAT enabled.

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 confidence

A race condition in F5 SSL Orchestrator 14.1.0-14.1.0.5 can cause TMM to restart when SSL Forward Proxy enforces the bypass action on a transparent virtual server with SNAT enabled. This is a rare timing-dependent bug specific to the interaction between SSL bypass enforcement and SNAT in the transparent proxy flow.

MitigationUpgrade to a later version of F5 SSL Orchestrator (14.1.0.6 or later) where the race condition has been resolved, or review SSL Orchestrator topology configurations to avoid the specific combination of transparent virtual server with SNAT and SSL forward proxy bypass if upgrade is not immediately feasible.

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
Ssl OrchestratorApplication
Affected:>= 14.1.0, < 14.1.0.6

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify SSL Orchestrator version
    Run 'tmsh show /sys software' or check the SSL Orchestrator version in the GUI under SSL Orchestrator > Overview. Compare the version to the affected range 14.1.0-14.1.0.5.
    Affected if The installed version is 14.1.0 through 14.1.0.5.
  2. Confirm SSL Forward Proxy is enabled
    Inspect the SSL Orchestrator topology configuration via 'tmsh list /sslo-ssl-orchestrator topology' or via the GUI under the specific topology settings. Look for SSL Forward Proxy mode being enabled.
    Affected if SSL Forward Proxy is turned on in the topology configuration.
  3. Identify if a transparent virtual server is in use
    Review the SSL Orchestrator topology configuration and locate the associated virtual server. Check if the virtual server type is set to Transparent (not Performance L4 or Standard).
    Affected if The topology uses a transparent virtual server type.
  4. Check if SNAT is enabled on the virtual server
    Examine the virtual server bound to the SSL Orchestrator topology via 'tmsh list /ltm virtual' and look for SNAT settings (Snatpool or Auto Map) applied to the transparent virtual server.
    Affected if SNAT is configured on the transparent virtual server.
  5. Verify bypass action is configured
    Review the SSL Orchestrator topology service policy or iRule configuration to determine if a bypass action (such as bypass-all, bypass-ssl, or selective bypass) is set to enforce on traffic.
    Affected if A bypass action is configured to enforce on the topology.

You are affected only if all five conditions are true: the version is 14.1.0-14.1.0.5, SSL Forward Proxy is enabled, a transparent virtual server is used, SNAT is enabled on that virtual server, and a bypass action is configured.

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 14.1.0.6 or later
Fixed in 14.1.0.6
Interim mitigation

Upgrade to a later version of F5 SSL Orchestrator (14.1.0.6 or later) where the race condition has been resolved, or review SSL Orchestrator topology configurations to avoid the specific combination of transparent virtual server with SNAT and SSL forward proxy bypass if upgrade is not immediately feasible.

Fix this in Ssl Orchestrator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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