{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-6686 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-6686 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-6686 is a medium-severity denial of service vulnerability in F5 Big-Ip Local Traffic Manager, published on 23 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-6686 and fix it if it is affected.\n\nWhat it is: CVE-2019-6686 is a medium-severity denial of service vulnerability in F5 Big-Ip Local Traffic Manager, published on 23 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-6686 in the wild and no public exploit code.\n\nAffected product: F5 Big-Ip Local Traffic Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-6686/ (Markdown: https://insights.sbomify.com/CVE-2019-6686/index.md)","id":"CVE-2019-6686","markdown":"https://insights.sbomify.com/CVE-2019-6686/index.md","name":"CVE-2019-6686","record":{"aliases":["GHSA-26hq-r45f-3pr8"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"BIG-IP load balancer","requires_auth":"none","summary":"An attacker can cause the Traffic Management Microkernel to stop responding by exhausting diameter connection limits, leading to a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"f5","cpe":[{"product":"big-ip_local_traffic_manager","vendor":"f5"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[],"description":"On BIG-IP versions 15.0.0-15.0.1.1, 14.1.0-14.1.2, 14.0.0-14.0.1, 13.1.0-13.1.3.1, the Traffic Management Microkernel (TMM) might stop responding after the total number of diameter connections and pending messages on a single virtual server has reached 32K.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Denial of service in BIG-IP","id":"CVE-2019-6686","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"f5:big-ip_local_traffic_manager","products":["f5:big-ip_local_traffic_manager"],"type":"denial_of_service","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Weak cryptography in BIG-IP ASM","id":"CVE-2019-6687"},"packages":[],"prev":{"headline":"Privilege escalation in BIG-IP","id":"CVE-2019-6685"},"products":["BIG-IP"],"published":"2019-12-23","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2016-5745","kev_date_added":null,"published":"2016-10-05"},{"cvss_score":7.5,"headline":"Denial of service in BIG-IP LTM","id":"CVE-2020-5936","kev_date_added":null,"published":"2020-10-29"},{"cvss_score":7.5,"headline":"Denial of service in BIG-IP","id":"CVE-2019-6681","kev_date_added":null,"published":"2019-12-23"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2018-17539","kev_date_added":null,"published":"2018-12-28"},{"cvss_score":6.2,"headline":"Path traversal in n/a","id":"CVE-2014-8727","kev_date_added":null,"published":"2014-11-17"},{"cvss_score":5.9,"headline":"Denial of service in BIG-IP (LTM)","id":"CVE-2019-6590","kev_date_added":null,"published":"2019-02-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["F5"]},"summary":"An attacker can cause the Traffic Management Microkernel to stop responding by exhausting diameter connection limits, leading to a denial of service.","url":"https://insights.sbomify.com/CVE-2019-6686/"}