CVE-2012-10022 affects Kloxo 6.1.12 and earlier. The product ships with two setuid-root binaries, lxsuexec and lxrestart. According to the provided content, lxsuexec performs a UID-based authorization check and allows execution of arbitrary commands as root when the invoking user is UID 48. Because UID 48 is typically associated with the Apache/web-server context on affected systems, an attacker who has obtained code execution or shell access in that context can invoke the vulnerable setuid binary and execute commands with root privileges. This is a local privilege-escalation vulnerability caused by improper privilege management and reliance on an unsafe identity check in a setuid-root program.
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 single Metasploit module (modules/exploits/linux/local/kloxo_lxsuexec.rb) targeting a local privilege escalation vulnerability in Kloxo versions 6.1.12 and earlier (CVE-2012-10022). The exploit abuses the setuid root binaries 'lxsuexec' and 'lxrestart' to escalate privileges from the 'apache' user (UID 48) to root. The module checks the current UID, writes a Metasploit-generated payload to a temporary file in /tmp, and uses the vulnerable binaries to execute the payload as root. The exploit is operational and provides a root shell if successful. The main fingerprintable endpoints are the setuid binaries '/usr/sbin/lxrestart', the temporary files in '/tmp', and the '/etc/passwd' file for user enumeration. The code is written in Ruby and is structured as a standard Metasploit local exploit module.
5 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.