{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-5892 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5892 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-5892 is a medium-severity denial of service vulnerability in n/a, published on 10 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-5892 and fix it if it is affected.\n\nWhat it is: CVE-2019-5892 is a medium-severity denial of service vulnerability in n/a, published on 10 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-5892 in the wild and no public exploit code.\n\nAffected product: n/a. 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-5892/ (Markdown: https://insights.sbomify.com/CVE-2019-5892/index.md)","id":"CVE-2019-5892","markdown":"https://insights.sbomify.com/CVE-2019-5892/index.md","name":"CVE-2019-5892","record":{"aliases":["GHSA-546m-4w73-87m7"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"FRRouting BGP daemon","requires_auth":"low_privilege","summary":"Remote attackers can cause BGP session flaps and denial of service in FRRouting when VNC is enabled, due to improper handling of specific BGP attributes.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"frrouting","vendor":"frrouting"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-436","name":"Interpretation Conflict"}],"description":"bgpd in FRRouting FRR (aka Free Range Routing) 2.x and 3.x before 3.0.4, 4.x before 4.0.1, 5.x before 5.0.2, and 6.x before 6.0.2 (not affecting Cumulus Linux or VyOS), when ENABLE_BGP_VNC is used for Virtual Network Control, allows remote attackers to cause a denial of service (peering session flap) via attribute 255 in a BGP UPDATE packet. This occurred during Disco in January 2019 because FRR does not implement RFC 7606, and therefore the packets with 255 were considered invalid VNC data and the BGP session was closed.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Denial of service in n/a","id":"CVE-2019-5892","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2019"},"n_packages":0,"n_references":7,"next":{"headline":"SQL injection in n/a","id":"CVE-2019-5893"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2019-5891"},"products":["n/a"],"published":"2019-01-10","related":[{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2024-44070","kev_date_added":null,"published":"2024-08-19"},{"cvss_score":9.8,"headline":"bgpd/bgp_flowspec.c in FRRouting (FRR) before 8.4.3 mishandles an nlri length of zero, aka a \"flowspec overflow.\"","id":"CVE-2023-38406","kev_date_added":null,"published":"2023-11-06"},{"cvss_score":8.1,"headline":"Use after free in n/a","id":"CVE-2022-37035","kev_date_added":null,"published":"2022-08-02"},{"cvss_score":7.8,"headline":"Memory corruption in FRRouting","id":"CVE-2022-26127","kev_date_added":null,"published":"2022-03-03"},{"cvss_score":7.8,"headline":"Memory corruption in FRRouting","id":"CVE-2022-26128","kev_date_added":null,"published":"2022-03-03"},{"cvss_score":7.8,"headline":"Memory corruption in FRRouting","id":"CVE-2022-26129","kev_date_added":null,"published":"2022-03-03"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2026-37457","kev_date_added":null,"published":"2026-05-01"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Remote attackers can cause BGP session flaps and denial of service in FRRouting when VNC is enabled, due to improper handling of specific BGP attributes.","url":"https://insights.sbomify.com/CVE-2019-5892/"}