Skip to content
Fencer Intel
high 7.5

CVE-2019-6612 json

On BIG-IP 14.0.0-14.1.0.1, 13.0.0-13.1.1.4, 12.1.0-12.1.4, 11.6.1-11.6.3.4, and 11.5.2-11.5.8, DNS query TCP connections that are aborted b…

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

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

Summary

On BIG-IP 14.0.0-14.1.0.1, 13.0.0-13.1.1.4, 12.1.0-12.1.4, 11.6.1-11.6.3.4, and 11.5.2-11.5.8, DNS query TCP connections that are aborted before receiving a response from a DNS cache may cause TMM to restart.

Patch / fix

  • f5 big-ip_access_policy_manager 11.5.9, 11.6.4, 12.1.4.1, 13.1.1.5, 14.1.0.2
  • f5 big-ip_advanced_firewall_manager 11.5.9, 11.6.4, 12.1.4.1, 13.1.1.5, 14.1.0.2
  • f5 big-ip_application_acceleration_manager 11.5.9, 11.6.4, 12.1.4.1, 13.1.1.5, 14.1.0.2
  • f5 big-ip_link_controller 11.5.9, 11.6.4, 12.1.4.1, 13.1.1.5, 14.1.0.2
  • f5 big-ip_policy_enforcement_manager 11.5.9, 11.6.4, 12.1.4.1, 13.1.1.5, 14.1.0.2
  • f5 big-ip_application_security_manager 11.5.9, 11.6.4, 12.1.4.1, 13.1.1.5, 14.1.0.2
  • f5 big-ip_local_traffic_manager 11.5.9, 11.6.4, 12.1.4.1, 13.1.1.5, 14.1.0.2
  • f5 big-ip_global_traffic_manager 11.5.9, 11.6.4, 12.1.4.1, 13.1.1.5, 14.1.0.2
  • f5 big-ip_domain_name_system 11.5.9, 11.6.4, 12.1.4.1, 13.1.1.5, 14.1.0.2

Is CVE-2019-6612 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.77% chance of exploitation in the next 30 days, higher than 78% 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 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Affected products

  • F5 BIG-IP (LTM, AAM, AFM, APM, ASM, DNS, GTM, Link Controller, PEM)

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.