Skip to content
Fencer Intel
high 7.2

CVE-2019-6620 json

On BIG-IP 14.1.0-14.1.0.5, 14.0.0-14.0.0.5, 13.0.0-13.1.1.4, 12.1.0-12.1.4.1, and 11.5.1-11.6.4 and BIG-IQ 6.0.0-6.1.0 and 5.1.0-5.4.0, an…

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

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

Summary

On BIG-IP 14.1.0-14.1.0.5, 14.0.0-14.0.0.5, 13.0.0-13.1.1.4, 12.1.0-12.1.4.1, and 11.5.1-11.6.4 and BIG-IQ 6.0.0-6.1.0 and 5.1.0-5.4.0, an undisclosed iControl REST worker vulnerable to command injection for an Administrator user.

Patch / fix

  • f5 big-ip_access_policy_manager 13.1.1.5, 14.1.0.6
  • f5 big-ip_advanced_firewall_manager 13.1.1.5, 14.1.0.6
  • f5 big-ip_application_acceleration_manager 13.1.1.5, 14.1.0.6
  • f5 big-ip_link_controller 13.1.1.5, 14.1.0.6
  • f5 big-ip_policy_enforcement_manager 13.1.1.5, 14.1.0.6
  • f5 big-ip_webaccelerator 13.1.1.5, 14.1.0.6
  • f5 big-ip_application_security_manager 13.1.1.5, 14.1.0.6
  • f5 big-ip_local_traffic_manager 13.1.1.5, 14.1.0.6
  • f5 big-ip_fraud_protection_service 13.1.1.5, 14.1.0.6
  • f5 big-ip_global_traffic_manager 13.1.1.5, 14.1.0.6
  • f5 big-ip_analytics 13.1.1.5, 14.1.0.6
  • f5 big-ip_edge_gateway 13.1.1.5, 14.1.0.6
  • f5 big-ip_domain_name_system 13.1.1.5, 14.1.0.6

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

CVSS scores

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

Affected products

  • F5 BIG-IP, BIG-IQ

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command

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.