Skip to content
Fencer Intel
medium 5.9

CVE-2020-5935 json

On BIG-IP (LTM, AAM, AFM, Analytics, APM, ASM, DNS, FPS, GTM, Link Controller, PEM) versions 15.1.0-15.1.0.5, 14.1.0-14.1.2.3, and 13.1.0-1…

published 6y ago modified 4mo ago also EUVD-2020-27089

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

Summary

On BIG-IP (LTM, AAM, AFM, Analytics, APM, ASM, DNS, FPS, GTM, Link Controller, PEM) versions 15.1.0-15.1.0.5, 14.1.0-14.1.2.3, and 13.1.0-13.1.3.3, when handling MQTT traffic through a BIG-IP virtual server associated with an MQTT profile and an iRule performing manipulations on that traffic, TMM may produce a core file.

Patch / fix

  • f5 big-ip_access_policy_manager 13.1.3.4, 14.1.2.4, 15.1.1
  • f5 big-ip_advanced_firewall_manager 13.1.3.4, 14.1.2.4, 15.1.1
  • f5 big-ip_analytics 13.1.3.4, 14.1.2.4, 15.1.1
  • f5 big-ip_application_acceleration_manager 13.1.3.4, 14.1.2.4, 15.1.1
  • f5 big-ip_application_security_manager 13.1.3.4, 14.1.2.4, 15.1.1
  • f5 big-ip_domain_name_system 13.1.3.4, 14.1.2.4, 15.1.1
  • f5 big-ip_fraud_protection_service 13.1.3.4, 14.1.2.4, 15.1.1
  • f5 big-ip_global_traffic_manager 13.1.3.4, 14.1.2.4, 15.1.1
  • f5 big-ip_link_controller 13.1.3.4, 14.1.2.4, 15.1.1
  • f5 big-ip_local_traffic_manager 13.1.3.4, 14.1.2.4, 15.1.1
  • f5 big-ip_policy_enforcement_manager 13.1.3.4, 14.1.2.4, 15.1.1

Is CVE-2020-5935 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

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

CVSS scores

assigned by version score vector
NVD 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Affected products

  • n/a BIG-IP (LTM, AAM, AFM, Analytics, APM, ASM, DNS, FPS, 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.