Loading vulnerability…
Pardus LightDM Greeter versions before 0.4.15 assign incorrect permissions to a critical resource. The misconfigured access-control security levels can allow unauthorized access to or manipulation of that resource.
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.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This two-file Python proof-of-concept repository contains a README and the executable `exploit.py` (approximately 45 KB). It targets the claimed CVE-2026-79617 in Pardus `pardus-lightdm-greeter` versions through 0.4.13. The stated flaw is an unconditional `xhost +local:` invocation at greeter startup, which permits every local OS user to connect to the active X server without an Xauthority cookie. The script is a local-session-hijacking exploit rather than a remote network exploit. It uses python-xlib and the XTEST extension to connect to the default `:0` display, enumerate X windows, capture screenshots, activate a selected/focused window, and synthesize keyboard input. It includes non-destructive check-only and evidence modes, but also active post-exploitation modes: arbitrary text/command injection, victim-session xterm spawning, reverse-shell handling, SSH authorized-key persistence, and cron-based reverse-shell persistence. The script records structured logs and saves metadata/evidence to a caller-selected output directory. No static remote command-and-control URL, IP address, domain, or fixed TCP/UDP endpoint is embedded in the visible code; reverse-shell host and port values are supplied at runtime via command-line arguments.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.