Loading vulnerability…
CVE-2017-5618 affects GNU screen before 4.5.1. The vulnerability arises from improper checking of logfile permissions, allowing a local user to cause screen to modify arbitrary files. Because screen is installed setuid root on many systems, this arbitrary file modification can be leveraged to escalate privileges to root.
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 contains a local privilege escalation exploit targeting GNU Screen version 4.5.0 (CVE-2017-5618). The exploit abuses insecure file permissions to overwrite /etc/ld.so.preload, causing the system to load a malicious shared object on subsequent executions. The provided bash script (in the README) automates the process: it creates a malicious shared library (/tmp/libhax.so) and a setuid root shell binary (/tmp/rootshell), then uses GNU Screen to create /etc/ld.so.preload with world-writable permissions, pointing to the attacker's library. When the library is loaded, it sets the setuid bit on the shell binary, granting root access. The repository includes a detailed README with step-by-step instructions and screenshots, but does not contain standalone exploit scripts or binaries—only the exploit logic and code snippets are present in the documentation. The exploit is operational and provides a working local root shell on vulnerable systems. No network endpoints are involved; all actions are performed locally on the target system.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.