Skip to content
Fencer Intel
high 7.5

CVE-2019-6680 json

On BIG-IP versions 15.0.0-15.0.1, 14.1.0-14.1.2, 14.0.0-14.0.1, 13.1.0-13.1.3.2, 12.1.0-12.1.5, and 11.5.2-11.6.5, while processing traffic…

published 6y ago modified 4mo ago also EUVD-2019-16239

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 64%
public exploits
0
none known

Summary

On BIG-IP versions 15.0.0-15.0.1, 14.1.0-14.1.2, 14.0.0-14.0.1, 13.1.0-13.1.3.2, 12.1.0-12.1.5, and 11.5.2-11.6.5, while processing traffic through a standard virtual server that targets a FastL4 virtual server (VIP on VIP), hardware appliances may stop responding.

Patch / fix

  • f5 big-ip_access_policy_manager 11.6.5.1, 14.0.1.1, 14.1.2.1, 15.0.1.1
  • f5 big-ip_advanced_firewall_manager 11.6.5.1, 14.0.1.1, 14.1.2.1, 15.0.1.1
  • f5 big-ip_analytics 11.6.5.1, 14.0.1.1, 14.1.2.1, 15.0.1.1
  • f5 big-ip_application_acceleration_manager 11.6.5.1, 14.0.1.1, 14.1.2.1, 15.0.1.1
  • f5 big-ip_application_security_manager 11.6.5.1, 14.0.1.1, 14.1.2.1, 15.0.1.1
  • f5 big-ip_domain_name_system 11.6.5.1, 14.0.1.1, 14.1.2.1, 15.0.1.1
  • f5 big-ip_fraud_protection_service 11.6.5.1, 14.0.1.1, 14.1.2.1, 15.0.1.1
  • f5 big-ip_global_traffic_manager 11.6.5.1, 14.0.1.1, 14.1.2.1, 15.0.1.1
  • f5 big-ip_link_controller 11.6.5.1, 14.0.1.1, 14.1.2.1, 15.0.1.1
  • f5 big-ip_local_traffic_manager 11.6.5.1, 14.0.1.1, 14.1.2.1, 15.0.1.1
  • f5 big-ip_policy_enforcement_manager 11.6.5.1, 14.0.1.1, 14.1.2.1, 15.0.1.1

Is CVE-2019-6680 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.06% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 7.8 AV:N/AC:L/Au:N/C:N/I:N/A:C

Affected products

  • F5 BIG-IP

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.