{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-9970 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-9970 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-9970 is a medium-severity vulnerability in n/a, published on 24 Mar 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-9970 and fix it if it is affected.\n\nWhat it is: CVE-2019-9970 is a medium-severity vulnerability in n/a, published on 24 Mar 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-9970 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-9970/ (Markdown: https://insights.sbomify.com/CVE-2019-9970/index.md)","id":"CVE-2019-9970","markdown":"https://insights.sbomify.com/CVE-2019-9970/index.md","name":"CVE-2019-9970","record":{"aliases":["GHSA-9p53-vpmw-2w5c"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Signal messaging app","requires_auth":"none","summary":"Attackers can spoof URLs using IDN homographs in Signal messages, tricking users into clicking malicious links due to visual character similarity.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"private_messenger","vendor":"signal"},{"product":"signal-desktop","vendor":"signal"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[],"description":"Open Whisper Signal (aka Signal-Desktop) through 1.23.1 and the Signal Private Messenger application through 4.35.3 for Android are vulnerable to an IDN homograph attack when displaying messages containing URLs. This occurs because the application produces a clickable link even if (for example) Latin and Cyrillic characters exist in the same domain name, and the available font has an identical representation of characters from different alphabets.","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":"Other in n/a","id":"CVE-2019-9970","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2019-9971"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-9969"},"products":["n/a"],"published":"2019-03-24","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":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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can spoof URLs using IDN homographs in Signal messages, tricking users into clicking malicious links due to visual character similarity.","url":"https://insights.sbomify.com/CVE-2019-9970/"}