{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-8960 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-8960 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-8960 is a high-severity denial of service vulnerability in n/a, published on 21 Apr 2020. 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-8960 and fix it if it is affected.\n\nWhat it is: CVE-2019-8960 is a high-severity denial of service vulnerability in n/a, published on 21 Apr 2020. 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-8960 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-8960/ (Markdown: https://insights.sbomify.com/CVE-2019-8960/index.md)","id":"CVE-2019-8960","markdown":"https://insights.sbomify.com/CVE-2019-8960/index.md","name":"CVE-2019-8960","record":{"aliases":["GHSA-j42p-4m2g-2gc3"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"FlexNet Publisher","requires_auth":"none","summary":"An attacker can cause a denial of service in FlexNet Publisher by sending a specific message that triggers an exception and terminates the process.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"flexera","cpe":[{"product":"flexnet_publisher","vendor":"flexera"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"}],"description":"A Denial of Service vulnerability related to command handling has been identified in FlexNet Publisher lmadmin.exe version 11.16.2. The message reading function used in lmadmin.exe can, given a certain message, call itself again and then wait for a further message. With a particular flag set in the original message, but no second message received, the function eventually return an unexpected value which leads to an exception being thrown. The end result can be process termination.","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 n/a","id":"CVE-2019-8960","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2019-8961"},"packages":[],"prev":{"headline":"Use after free in Linux Kernel","id":"CVE-2019-8956"},"products":["n/a"],"published":"2020-04-21","related":[{"cvss_score":9.8,"headline":"Memory corruption in FlexNet Publisher","id":"CVE-2018-20033","kev_date_added":null,"published":"2019-02-25"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2019-8963","kev_date_added":null,"published":"2023-03-29"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2020-12080","kev_date_added":null,"published":"2021-09-17"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2020-12081","kev_date_added":null,"published":"2020-07-31"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2019-8961","kev_date_added":null,"published":"2020-04-21"},{"cvss_score":7.5,"headline":"Denial of service in FlexNet Publisher","id":"CVE-2018-20031","kev_date_added":null,"published":"2019-03-21"}],"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":"An attacker can cause a denial of service in FlexNet Publisher by sending a specific message that triggers an exception and terminates the process.","url":"https://insights.sbomify.com/CVE-2019-8960/"}