{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17192 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-17192 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-17192 is a critical denial of service vulnerability in n/a, published on 5 Oct 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-17192 and fix it if it is affected.\n\nWhat it is: CVE-2019-17192 is a critical denial of service vulnerability in n/a, published on 5 Oct 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-17192 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-17192/ (Markdown: https://insights.sbomify.com/CVE-2019-17192/index.md)","id":"CVE-2019-17192","markdown":"https://insights.sbomify.com/CVE-2019-17192/index.md","name":"CVE-2019-17192","record":{"aliases":["GHSA-228q-pr2f-pghm"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Signal Android app","requires_auth":"none","summary":"Remote attackers can cause denial of service in Signal for Android by sending malformed RTP packets before a call is answered.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"private_messenger","vendor":"signal"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-670","name":"Always-Incorrect Control Flow Implementation"}],"description":"The WebRTC component in the Signal Private Messenger application through 4.47.7 for Android processes videoconferencing RTP packets before a callee chooses to answer a call, which might make it easier for remote attackers to cause a denial of service or possibly have unspecified other impact via malformed packets. NOTE: the vendor plans to continue this behavior for performance reasons unless a WebRTC design change occurs","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-17192","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Improper Check for Unusual or Exceptional Conditions in Connect2id Nimbus JOSE+JWT","id":"CVE-2019-17195"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2019-17191"},"products":["n/a"],"published":"2019-10-05","related":[{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2019-17191","kev_date_added":null,"published":"2019-10-05"},{"cvss_score":6.5,"headline":"Other in n/a","id":"CVE-2019-9970","kev_date_added":null,"published":"2019-03-24"},{"cvss_score":5.3,"headline":"Information disclosure in Signal Private Messenger","id":"CVE-2020-5753","kev_date_added":null,"published":"2020-05-20"},{"cvss_score":3.3,"headline":"Information disclosure in Signal","id":"CVE-2018-3988","kev_date_added":null,"published":"2018-12-10"}],"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-05","vendors":["n/a"]},"summary":"Remote attackers can cause denial of service in Signal for Android by sending malformed RTP packets before a call is answered.","url":"https://insights.sbomify.com/CVE-2019-17192/"}