Loading vulnerability…
Deepin Linux deepin-reader versions before 6.0.7 contain a design flaw that permits a crafted DOCX document to overwrite files. An attacker can overwrite shell initialization files, causing command execution when the affected user subsequently opens a terminal.
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 provides a proof-of-concept exploit for CVE-2023-50254, a remote code execution vulnerability in Deepin Linux's default document viewer, deepin-reader. The exploit leverages a design flaw where deepin-reader, when opening a .docx file, extracts its contents and uses the 'pandoc' utility to convert a file to HTML. By crafting a malicious .docx file containing a symlink (word/temp.html) pointing to a sensitive file (such as the user's .bashrc), the exploit causes pandoc to overwrite that file with attacker-controlled content. The provided Bash script, 'deepin-reader_exploit.sh', automates the creation of such a malicious .docx file from a user-supplied text file and command. The exploit is effective when a Deepin Linux user opens the crafted document with deepin-reader, leading to file overwrite and potential remote code execution upon the next terminal session. The repository consists of a README.md explaining the vulnerability and exploit steps, and a Bash script that generates the exploit document. No network endpoints are involved; the attack is local and targets file system paths.
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.