{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-5753 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-5753 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-5753 is a medium-severity vulnerability in Signal Private Messenger, published on 20 May 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-2020-5753 and fix it if it is affected.\n\nWhat it is: CVE-2020-5753 is a medium-severity vulnerability in Signal Private Messenger, published on 20 May 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-2020-5753 in the wild and no public exploit code.\n\nAffected product: Signal Private Messenger. 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-2020-5753/ (Markdown: https://insights.sbomify.com/CVE-2020-5753/index.md)","id":"CVE-2020-5753","markdown":"https://insights.sbomify.com/CVE-2020-5753/index.md","name":"CVE-2020-5753","record":{"aliases":["GHSA-cqgm-mqmr-px3p"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Signal Private Messenger","requires_auth":"none","summary":"Remote attackers can disclose the victim's DNS server and ring their phone via ICE Candidate handling flaws in Signal mobile apps.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"tenable","cpe":[{"product":"private_messenger","vendor":"signal"},{"product":"signal","vendor":"signal"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-670","name":"Always-Incorrect Control Flow Implementation"}],"description":"Signal Private Messenger Android v4.59.0 and up and iOS v3.8.1.5 and up allows a remote non-contact to ring a victim's Signal phone and disclose currently used DNS server due to ICE Candidate handling before call is answered or declined.","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":"Information disclosure in Signal Private Messenger","id":"CVE-2020-5753","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Webroot SecureAnywhere","id":"CVE-2020-5754"},"packages":[],"prev":{"headline":"Path traversal in Druva inSync Windows Client","id":"CVE-2020-5752"},"products":["Signal Private Messenger"],"published":"2020-05-20","related":[{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2019-17192","kev_date_added":null,"published":"2019-10-05"},{"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":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-04","vendors":["n/a"]},"summary":"Remote attackers can disclose the victim's DNS server and ring their phone via ICE Candidate handling flaws in Signal mobile apps.","url":"https://insights.sbomify.com/CVE-2020-5753/"}