Skip to content
Fencer Intel
high 7.5

CVE-2019-6605 json

On BIG-IP 11.5.1-11.5.8, 11.6.1-11.6.3, and 12.0.x, an undisclosed sequence of packets received by an SSL virtual server and processed by a…

published 7y ago modified 4mo ago also EUVD-2019-16164

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

Summary

On BIG-IP 11.5.1-11.5.8, 11.6.1-11.6.3, and 12.0.x, an undisclosed sequence of packets received by an SSL virtual server and processed by an associated Client SSL or Server SSL profile may cause a denial of service.

Patch / fix

  • f5 big-ip_access_policy_manager 11.5.9, 11.6.4, 12.1.0
  • f5 big-ip_advanced_firewall_manager 11.5.9, 11.6.4, 12.1.0
  • f5 big-ip_application_acceleration_manager 11.5.9, 11.6.4, 12.1.0
  • f5 big-ip_edge_gateway 11.5.9, 11.6.4, 12.1.0
  • f5 big-ip_fraud_protection_service 11.5.9, 11.6.4, 12.1.0
  • f5 big-ip_global_traffic_manager 11.5.9, 11.6.4, 12.1.0
  • f5 big-ip_link_controller 11.5.9, 11.6.4, 12.1.0
  • f5 big-ip_local_traffic_manager 11.5.9, 11.6.4, 12.1.0
  • f5 big-ip_policy_enforcement_manager 11.5.9, 11.6.4, 12.1.0
  • f5 big-ip_webaccelerator 11.5.9, 11.6.4, 12.1.0
  • f5 big-ip_analytics 11.5.9, 11.6.4, 12.1.0
  • f5 big-ip_application_security_manager 11.5.9, 11.6.4, 12.1.0
  • f5 big-ip_protocol_security_manager 11.5.9, 11.6.4, 12.1.0

Is CVE-2019-6605 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.71% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected products

  • BIG-IP BIG-IP (LTM, AAM, AFM, Analytics, APM, ASM, DNS, Edge Gateway, FPS, GTM, Link Controller, PEM, WebAccelerator)

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.