CVE-2020-20093 is a user interface vulnerability in Facebook Messenger for iOS (versions 227.0 and prior) and Android (versions 228.1.0.10.116 and prior), where the app does not properly represent URI messages to the user. This allows attackers to craft messages containing specially formatted URIs that appear legitimate but actually direct users to malicious or unintended destinations.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository demonstrates a proof-of-concept exploit for RTLO (Right-To-Left Override) injection URI spoofing vulnerabilities affecting several popular messaging applications, including WhatsApp, iMessage, Instagram, Facebook Messenger, and Signal. The exploit targets CVE-2020-20093, CVE-2020-20094, CVE-2020-20095, and CVE-2020-20096, and is effective against specific versions of these apps on both iOS and Android platforms. The repository contains two main exploit files: - 'exploit.sh': A Bash script that generates spoofed URLs by combining a legitimate-looking prefix (https://legit.okay/files) with a set of attacker-controlled domains, inserting the Unicode RTLO character to reverse the display order of the URL. The output is a set of links that, when pasted into a vulnerable messaging app, appear to be legitimate but actually direct the user to a malicious site. - 'poc.py': A Python script that takes a legitimate website and an attacker website as arguments, and outputs a single spoofed link using the RTLO technique. This script allows for custom input and demonstrates the same vulnerability in a more flexible way. The exploit does not deliver a payload in the traditional sense (e.g., shellcode or remote code execution), but rather manipulates the visual representation of links to facilitate phishing or social engineering attacks. The endpoints involved are attacker-controlled domains and a legitimate-looking URL prefix. The exploit is a proof-of-concept and requires the attacker to send the crafted link to a victim via a vulnerable messaging app.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.