{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-9747 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-9747 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-9747 is a high-severity denial of service vulnerability in n/a, published on 13 Mar 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-9747 and fix it if it is affected.\n\nWhat it is: CVE-2019-9747 is a high-severity denial of service vulnerability in n/a, published on 13 Mar 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-9747 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-9747/ (Markdown: https://insights.sbomify.com/CVE-2019-9747/index.md)","id":"CVE-2019-9747","markdown":"https://insights.sbomify.com/CVE-2019-9747/index.md","name":"CVE-2019-9747","record":{"aliases":["GHSA-6729-2hp6-xxx8"],"analysis":{"component_type":"library","fix_type":"end_of_life","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"mDNS library","requires_auth":"none","summary":"A malicious mDNS packet causes an infinite loop in the tinysvcmdns library, hanging the server; the project is unmaintained and deprecated.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tinysvcmdns","vendor":"tinysvcmdns_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-835","name":"Loop with Unreachable Exit Condition"}],"description":"In tinysvcmdns through 2018-01-16, a maliciously crafted mDNS (Multicast DNS) packet triggers an infinite loop while parsing an mDNS query. When mDNS compressed labels point to each other, the function uncompress_nlabel goes into an infinite loop trying to analyze the packet with an mDNS query. As a result, the mDNS server hangs after receiving the malicious mDNS packet. NOTE: the product's web site states \"This project is un-maintained, and has been since 2013. ... There are known vulnerabilities ... You are advised to NOT use this library for any new projects / products.\"","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-9747","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":"Information disclosure in n/a","id":"CVE-2019-9748"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2019-9746"},"products":["n/a"],"published":"2019-03-13","related":[{"cvss_score":10,"headline":"Memory corruption in Tinysvcmdns","id":"CVE-2017-12087","kev_date_added":null,"published":"2018-04-24"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2019-9748","kev_date_added":null,"published":"2019-03-13"},{"cvss_score":7.5,"headline":"Null dereference in Tinysvcmdns","id":"CVE-2017-12130","kev_date_added":null,"published":"2018-01-20"}],"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-09-16","vendors":["n/a"]},"summary":"A malicious mDNS packet causes an infinite loop in the tinysvcmdns library, hanging the server; the project is unmaintained and deprecated.","url":"https://insights.sbomify.com/CVE-2019-9747/"}