{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-28345 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-28345 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-28345 is a high-severity vulnerability in n/a, published on 15 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-28345 and fix it if it is affected.\n\nWhat it is: CVE-2022-28345 is a high-severity vulnerability in n/a, published on 15 Apr 2022. 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-2022-28345 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-2022-28345/ (Markdown: https://insights.sbomify.com/CVE-2022-28345/index.md)","id":"CVE-2022-28345","markdown":"https://insights.sbomify.com/CVE-2022-28345/index.md","name":"CVE-2022-28345","record":{"aliases":["GHSA-9h9j-m9f5-4f79"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Signal iOS app","requires_auth":"none","summary":"Attackers can spoof URLs in Signal for iOS using RTLO injection to disguise malicious links as legitimate ones, bypassing user verification.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"signal","vendor":"signal"}],"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:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"The Signal app before 5.34 for iOS allows URI spoofing via RTLO injection. It incorrectly renders RTLO encoded URLs beginning with a non-breaking space, when there is a hash character in the URL. This technique allows a remote unauthenticated attacker to send legitimate looking links, appearing to be any website URL, by abusing the non-http/non-https automatic rendering of URLs. An attacker can spoof, for example, example.com, and masquerade any URL with a malicious destination. An attacker requires a subdomain such as gepj, txt, fdp, or xcod, which would appear backwards as jpeg, txt, pdf, and docx respectively.","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":"Other in n/a","id":"CVE-2022-28345","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"SQL Injection in Django","id":"CVE-2022-28346"},"packages":[],"prev":{"headline":"Path traversal in Trend Micro HouseCall for Home Networks","id":"CVE-2022-28339"},"products":["n/a"],"published":"2022-04-15","related":[{"cvss_score":8.6,"headline":"Denial of service in n/a","id":"CVE-2018-16132","kev_date_added":null,"published":"2018-08-29"},{"cvss_score":6.8,"headline":"Security feature bypass in n/a","id":"CVE-2018-9840","kev_date_added":null,"published":"2018-04-10"},{"cvss_score":1,"headline":"Signal App Biometric Authentication missing critical step in authentication","id":"CVE-2025-5715","kev_date_added":null,"published":"2025-06-06"}],"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-03","vendors":["n/a"]},"summary":"Attackers can spoof URLs in Signal for iOS using RTLO injection to disguise malicious links as legitimate ones, bypassing user verification.","url":"https://insights.sbomify.com/CVE-2022-28345/"}